I have a question whether it makes sense to use Comet's partialUpdate
or rather plain Ajax in the following situation:
On our site, the user can enter some piece of information which is
then ajax send to the server. Currently the call immediately returns,
which is desired.
On the server side some processing is done with that data in a
separate thread and when done the data is sent to a Comet Actor.
This actor then sends the data to the requesting user, and only to
him. There is no need to send the data to other browsers.
I choose Comet Actor for this because it takes a few seconds to
process the data, which I wanted to be done in a different thread. The
user can continue to work and when the processing is complete the data
appears in his browser.
Is that a use case for Comet (because it's only pushed to the same
browser it came from) or should I resort to plain Ajax? What's the
processing overhead for comet because it's send to every comet
If I should do that with plain Ajax, can I still process the request
in a different thread and answer the ajax call when complete?
Thanks for your help!