I am still not convinced that polling is a good solution for long queries.
One good reason for this is that you can't implement real time
application anymore: a chat board, real time stock quotes, etc...
Isn't it better to store the tcp socket file handles left open in a
connection pool?
As soon as a new event is to be sent, the tcp connection is retrieved
from the pool, then simply written.
If apache limit connection time, isn't it simpler to use another port
and let the javascript contact directly the webware application server
bypassing apache?
I don't know how many tcp connections can a single linux server can
handle, probably tens of thousand?
Maybe a persistant connection handler could be implemented in webware?
Anyway, you need to somehow inform the client that your result is
ready. For VERY long running queries, you can expect the client to
look at a certain result page. But John's solution is nice in that it
informs the client automatically when the server is ready, even if it
takes longer than the usual timeout of 90 seconds.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss
