From: "Eric Lehti"
The Oreilly book ... provides the programming code for two
examples of server push and contrasts that to client pull.
The discussion of the "Content-type: multipart/x-mixed-replace;boundary=End" header was interesting but misrepresented as a "push" technology. That term leads to confusion and misunderstanding. That seems to be the norm when discussing "push" technology.
The reason the sample is mislabeled is because it responds to just one request. It just does it incrementally, with intermittent sleep, and relies on a browser mechanism that allows a response to be sectioned into boundaries. The browser won't wait indefinitely. The server can't initiate the conversation. And the technique ties up a server resource so that the architecture won't scale.
It would be better to retire Chapter 6 altogether and use the window.setInterval() method in conjunction with AJAX.
Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
