I agree with the comments posted above.
I would, however, implement the “processor” as a separate page using ashx (handler), since they are really easy to call and poll from javascript, and you simply encode the process request event stream into the response stream.
I would like to show you an example on my site, but my host decided to spend a week from my site while they update .net on their servers (you can imagine that they did not particularly like it).
In fact, although in my case I have a page that uses data from: Bbc Google Amazon Amazon YouTube some other random sites.
The page will be returned to the user and individual controls on the page, then make ajax callbacks to the server for your parts.
The default content for tags into which feedback data will be loaded is a simple animated gif image that looks the same as a flash or silverlight boot circle.
As soon as the data is returned, the gif is replaced with the content uploaded by the server.
This means that the client sees “loading”, and the server is busy processing everything (seemingly synchronously from his point of view) that the client needs.
This is a clean user interface and the code is really simple.
I tried out the idea when I looked at how to download files using silverlight.
The basic concept:
- ajax call "ashx". (maybe 10 javascript lines)
- the server is processing the request. (depends on the complexity of the request, variables passed through the request)
- the answer fills 1 element on another page. (ajax cllback does this)
Hope this helps :)
source share