Large Data Streaming from Web Sevice to Client

Ask a Question related to ASP.NET Web Services, Design and Development.

  1. #1

    Default Large Data Streaming from Web Sevice to Client

    I want to create a search usecase on Client which will bring large data from
    webservice to the client.
    I am returning DataSet from the web service.
    What I want that Data Should come to the Client and start populating in the
    grid. Meanwhile if the user wants to Press cancel. He should cancel the
    search.
    In normal cases, all the DataSet is populated and is send to the client.
    Once the dataset reaches the client. Client shows it in DataGrid in one go.
    But i want the data to be streamed. The purpose is that client should not
    wait and start receiving the data and could press cancel at any moment.

    Regards
    Armoghan


    Armoghan Asif Guest

  2. Similar Questions and Discussions

    1. streaming recorded media by a client
      In this way, a client does not have to upload media files to an FMS server. He could store it on his local harddisk, and when he plays it,...
    2. Large hit live streaming web video site
      I have multiple large hit live streaming video sites. I use Axis cameras servers and they can only handle 20 users per server. I need to be able to...
    3. Problem with HTA streaming data to client
      Hi, I've an .aspx page which I call from a .hta in IE6 (so I can get rid of the window control buttons etc) When I call the .aspx page directly...
    4. Large Files, Dynamic Loading (Streaming)?
      I'm building a simple site of about 100 images that fade or cross fade. Every 10 images or so build a "scene." I want to avoid streaming a large...
    5. Example of Streaming response to client???
      Could you give me an example of streaming a page to the client? Thanks. Larry Woods
  3. #2

    Default Re: Large Data Streaming from Web Sevice to Client

    I explored such a scenario. The best I determine was it can't be done. I
    even made such a suggestion to Microsoft during the VS2005 beta cycle, but
    it didn't make it to implementation (at least in this product release). The
    suggestion seemed well received.

    The work-around solution I thought of is to have the initial web service
    call return some sort of small index table. Then, with a background thread,
    loop through the index table requesting the actual information one item at a
    time via web service calls.

    For example you might create a table with the fields RequestNo, ItemNo and
    ItemData. The initial web service call would perform it search. Say for
    example that 5 items are found. The web service generate a new unique
    RequestNo, and populate the table with the five items, returning RequestNo
    and the number of items. Then your app would loop 5 times using a thread,
    each time call requesting item n of RequestNo. And to be nice, you could
    then call a third method to flush the table of the RequestNo items.

    No, it not efficient in terms of cpu cycles, network traffic, etc. And it
    will take actually a larger time frame. But, it does allow the UI to
    response to the user and provide the ability to update the information as
    received, instead of all at once. As often stated, life is a trade off.

    But, if you happen to come up with a better idea, I would love to hear it.

    Richard Rosenheim



    "Armoghan Asif" <armoghan@adnare.com> wrote in message
    news:e3QCz1ghFHA.4000@TK2MSFTNGP12.phx.gbl...
    > I want to create a search usecase on Client which will bring large data
    from
    > webservice to the client.
    > I am returning DataSet from the web service.
    > What I want that Data Should come to the Client and start populating in
    the
    > grid. Meanwhile if the user wants to Press cancel. He should cancel the
    > search.
    > In normal cases, all the DataSet is populated and is send to the client.
    > Once the dataset reaches the client. Client shows it in DataGrid in one
    go.
    > But i want the data to be streamed. The purpose is that client should not
    > wait and start receiving the data and could press cancel at any moment.
    >
    > Regards
    > Armoghan
    >
    >

    Richard L Rosenheim 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