Jesper Sahner wrote:
My question is if it is possible - within the "http-framework" - to ask the server to return an answer when it has the answer instead of periodically asking for an answer which is basically waste of time.
HTTP is inherently a request/response protocol. You could issue a request and have server wait to respond until the desired data is available. But the socket would eventually timeout and you'd have to re-issue the request. Additionally, it needlessly ties up resources on the server.
By way of comparison how do Flash-driven websites which are dynamically updated (e.g. stock tickers) work in this context?
At least some of them are polling the server with requests every N seconds. Some can open raw sockets to the server, but these methods have trouble getting through firewalls. C -- ------------------------------------------------------------------------- Chris Merrill | http://www.webperformance.com Web Performance Inc. Website Load Testing and Stress Testing Software ------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
