W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 2001

RE: Server Push: Multipart/X-Mixed-Replace

From: John C. Mallery <jcma@ai.mit.edu>
Date: Fri, 27 Apr 2001 13:25:53 -0500
Message-Id: <p04320410b70f69a9d5b7@[128.52.39.204]>
To: "Miguel Estrada" <mestrada@infograficos.com>
Cc: <http-wg@hplb.hpl.hp.com>
Thanks, but this answer is not related to the question. We already implemented
from the documentation many years ago. Moreover, netscape 6 does not
implement server push (more code base forgetting).

Does anybody know the current status of this feature from netscape browsers
prior to 6?

This is a useful feature and perhaps there should be an RFC documenting it
so that it is preserved in mainstream browsers.

One useful application would be incremental redisplay, whereby the diffs
are sent during the refresh.  This goes beyond the netscape spec, but this
facility could do it.  For example, one could provide element IDs that should be
updated with the new data.


At 21:34 +0200 2001-04-24, Miguel Estrada wrote:
>Hi,
>
>You can find this info in the Netscape web site, bud is not implemented in
>Internet Explorer.
>
>
>Miguel Estrada
>
>
>
>----- Original Message -----
>From: John C. Mallery <jcma@ai.mit.edu>
>To: <http-wg@hplb.hpl.hp.com>
>Sent: Sunday, April 22, 2001 10:03 PM
>Subject: Server Push: Multipart/X-Mixed-Replace
>
>
>> Does anybody know the current status of this feature from netscape
>browsers
>> prior to 6?
>>
>> This is a useful feature and perhaps there should be an RFC documenting it
>> so that it is preserved in mainstream browsers.
>>
>> One useful application would be incremental redisplay, whereby the diffs
>> are sent during the refresh.  This goes beyond the netscape spec, but this
>> facility could do it.  For example, one could provide element IDs that
>should be
>> updated with the new data.
>>
>>
>>
>>
Received on Friday, 27 April 2001 21:37:44 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:43 EDT