OK-- so this solution is similar to maintaining a persistent non-HTTP
connection, but has the advantage of being implemented as pure HTTP.
Actually, it works just like HTTP/1.1's persistent connections except that the
server pushes the next response to the client and there is no limit on the
number of responses on any given connection.
Does it work with Proxy servers? I would imagine that it will work with some,
but not others-- it depends on how transparent the proxy server is when
dealing with a "live" HTTP connection.
It would appear that this will have the same scalability consequences as other
persistent connection schemes-- and, in some cases, worse consequences.
If each client using server push requires a persistent connection, that will
result in each server maintaining potentially hundrends or thousands of active
TCP/IP connections for a heavily used site.
b.bum
