Quoting Eli Marmor, from the post of Wed, 30 Oct: > There are actually 3 methods, and not one. > > The main one doesn't work well with some of the proxies, and is > probably exactly what you guessed. > > I don't speak about black-magics,
well, do share, and stop talking in riddles like you invented the moon? I have no idea how a webserver can tell the client something asynchronously (not as an answer to a request), and if you don't end the reply of the server (i.e. keep sending more info), the client can't make new requests. the only way that comes to mind is opening one connection, recieving a cookie, opening a second connection, quoting the cookie, have the webserver tie the two sessions together, and then the client sends requests on one (and gets simple empty replies fpr HTTP compliance) and the real replies come down the other connection as a long neverending "reply". the problems you still face are impatiant proxies closing the connection, or simply not supporting HTTP 1.1 -- Significant other Ira Abramov http://ira.abramov.org/email/ This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal. ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
