I agree with the comments posted above.
I would and have however implement the "processor" as a separate page using a ashx (handler) as these are really simple to call and poll from javascript and you simply code the process request event feeding stuff in to the response stream.
I'd love to show you an example on my site but my host has decided to have a week off running my site whilst they update .net on their servers (s you can imagine im not particularly pleased with this).
Essentially though in my case I have a page that relies on data from:
The bbc
google
amazon
youtube
some other random sites.
The page is returned to the user and the individual controls on the page then make ajax calls back to the server for their parts.
The default content for the tags in which the fed back data will be loaded in to is a simple animated gif image that looks much like a flash or silverlight loading circle.
Once the data comes back the gif is replaced with the server fed content.
This means the client sees "loading" and the server is busy handling everything (seemingly syncronously from its point of view) the client needs.
It's a clean user experience and the code is really simple.
I tripped over the idea when looking at how to do file uploading using silverlight.
Basic concept:
- ajax call to "ashx". (maybe 10 lines of javascript)
- server processes request. (depends on complexity of request, variables passed using querystring)
- response populates 1 element on otherwise complete page. (ajax cllback does this)
Hope this helps :)