It CAN be done with content-type: multipart/x-mixed-replace;boundary=foobar
Then when you need to update, just pop out another boundary and the rest
of the document.
There's probably a better way using HTTP 1.1 with keepalives, though.
Will Stranathan
Diethelm Guallar, Gonzalo wrote:
> We have at least two different projects where our clients have asked
> for the ability to send a proactive message to the client, advising
> him or her of an exceptional situation. As I understand things, this
> is not possible in a pure browser model, where the browser has a
> simple cycle of "read data, send to server, read response, show to
> user". Therefore, it seems obvious the requirements for proactive
> messages cannot be supported without some additional mechanism; I can
> see two ways out:
>
> 1. Have every page refresh itself every N seconds, and show proactive
> messages when they appear on the server. This is tantamount to
> polling, is an ugly hack, and I only mention it for completeness.
>
> 2. Have an applet running on the browser, listening on a specific
> port; when a message arrives, pass it on to the browser (probably
> via JavaScript) so that the browser can do something with it. This
> add listening functionality to the browser, and may open up a whole
> can of worms in terms of security.
>
> Does anybody have opinions on how this could be handled? Does Turbine
> provide any mechanism for this kind of functionality? If the applet is
> the way, anybody knows any open source components that implement this
> solution? Comments are welcome. Thanks,
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
