* Thus wrote Justin Patrin: > This wasn't really a reply to me but.... > > On Mon, 28 Jun 2004 09:20:14 -0700 (PDT), Matthew Sims > <[EMAIL PROTECTED]> wrote: > > > > > The PUSH thing you're referring to? Are you talking about the PSH flag in > > TCP? PUSH is a transport-layer protocal. HTTP only has GET and POST (as > > well as OPTION,HEAD,PUT,DELETE,TRACE and CONNECT) which are > > application-layered. > > I didn't refer to anything. Others did. You can't PUSH from the server > with HTTP it just doesn't work. The person asking about this needs to > sit down and look at how client/server works. To make this work as a > chat client, you have to poll or use sockets.
That was me that introduced the PUSH concept into this thread. Basically it was a method that netscape had introduced, mostly used with images but in theory html documents could be sent as well. As far as what browsers support this is unknown to me. The basic concept goes like this (of what the server sends to the client): Content-Type: multipart/replace; boundary="--uniqueboundary--" --uniqueboundary-- Content-Type: image/jpeg <jpeg contents> --uniqueboundary-- Content-Type: image/jpeg <a differnt jpeg contents> --uniqueboundary-- Content-Type: image/jpeg <yet another differnt jpeg contents> <continued till whenever the server whishes to end> --uniqueboundary---- And so the client would take each content within each boundary and replace what is displayed to the end user, all within one request. And that there is what is an HTTP push is :) Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
