Server PUSH to client

Ask a Question related to ASP.NET Building Controls, Design and Development.

  1. #1

    Default Server PUSH to client

    We have an internal asp.net application for orders/manufacturing
    information. Presently we have set the META Refresh tag on the affected
    pages set to "120" so the client browsers refresh every two minutes so
    displayed data is "current". This has several drawbacks, including the
    annoyance of a the refresh occurring while the user is viewing a page, and
    the fact that the great majority of refreshes are unnecessary as no data has
    changed.

    Is there a technique for sending updates from the Server to the Client when
    data is changed? Any suggestions?

    Thanks/


    PBS Guest

  2. Similar Questions and Discussions

    1. Can you push XML data with Media Server 2
      Can you use Media Server 2 to PUSH just regular data to a SWF say like XML data sent every second? THX Kevin
    2. Flash Webcam client <-> client (not client <-> server<-> client)
      Dear Flash Team, supporter and regular mortals (Like myself) I am currently running a IRC chat with mostly webclients connected. We currently offer...
    3. Server push
      Hi all, I have developed a PHP-based website where a "planner" user can make up schedules of activities to be performed, storing them into MySQL...
    4. how to do a server push
      At a certain page in my web app I'm entering users into a Queue for processing, how can I do a server push (like the expedia 'searching for...
    5. Push XML data to client for processing
      Hello, Although I consider myself a proficient C++ programmer (and am getting better everyday at C# :-) I am new to and having a little trouble...
  3. #2

    Default Re: Server PUSH to client

    > Is there a technique for sending updates from the Server to the Client
    > when data is changed? Any suggestions?
    HTTP is a request/response protocol. You'll have to work around that issue
    by building a polling system, which it already sounds like you're doing with
    the META Refresh tags. The other option is to use XmlHttp in javascript to
    make a request tot he server. This will avoid the refresh when no data has
    changed. Once your javascript does detect a chance, you can make the browser
    do a refresh.

    -Brock
    DevelopMentor
    [url]http://staff.develop.com/ballen[/url]





    Brock Allen Guest

  4. #3

    Default RE: Server PUSH to client

    hi,
    here are a couple of links to guide in the direction......

    [url]http://dotnetjunkies.com/WebLog/davetrux/archive/2004/06/16/16745.aspx[/url]

    [url]http://www.codeproject.com/jscript/refreshpartweb.asp[/url]

    regds
    Kannan.V

    "PBS" wrote:
    > We have an internal asp.net application for orders/manufacturing
    > information. Presently we have set the META Refresh tag on the affected
    > pages set to "120" so the client browsers refresh every two minutes so
    > displayed data is "current". This has several drawbacks, including the
    > annoyance of a the refresh occurring while the user is viewing a page, and
    > the fact that the great majority of refreshes are unnecessary as no data has
    > changed.
    >
    > Is there a technique for sending updates from the Server to the Client when
    > data is changed? Any suggestions?
    >
    > Thanks/
    >
    >
    >
    Kannan.V [MCSD.net] Guest

  5. #4

    Default Re: Server PUSH to client

    You could just add an iframe to your page and set the src of the iframe to
    an aspx page that will reload on a timer using meta refresh or a javascript
    timer. The iframe will reload its document without reloading the rest of
    the page.

    HTH

    Dale Preston
    MCAD, MCDBA, MCSE

    "PBS" <pbs@allwave.com> wrote in message
    news:ulEZiSqPFHA.904@TK2MSFTNGP10.phx.gbl...
    > We have an internal asp.net application for orders/manufacturing
    > information. Presently we have set the META Refresh tag on the affected
    > pages set to "120" so the client browsers refresh every two minutes so
    > displayed data is "current". This has several drawbacks, including the
    > annoyance of a the refresh occurring while the user is viewing a page, and
    > the fact that the great majority of refreshes are unnecessary as no data
    has
    > changed.
    >
    > Is there a technique for sending updates from the Server to the Client
    when
    > data is changed? Any suggestions?
    >
    > Thanks/
    >
    >

    Dale Preston Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139