W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1999

RE: Asynchronous updates/notifications

From: <kugler@us.ibm.com>
Date: Thu, 17 Jun 1999 10:17:03 -0600
To: "Scott Lawrence" <lawrence@agranat.com>
cc: http-wg@cuckoo.hpl.hp.com
Message-ID: <87256793.005991CC.00@d53mta08h.boulder.ibm.com>


Great!  Is the current MIME type still "multipart/x-mixed-replace" (i.e., is it
still considered experimental?)?  Is multipart/replace widely implemented?

     -Carl



"Scott Lawrence" <lawrence@agranat.com> on 06/17/99 08:21:45 AM

To:   Carl Kugler/Boulder/IBM@IBMUS, http-wg@cuckoo.hpl.hp.com
cc:
Subject:  RE: Asynchronous updates/notifications







> From: kugler@us.ibm.com

> For some long-running operations, it would be nice if a server
> could send asynchronous notifications to a client, so the client
> doesn't have to poll (or refresh periodically) to get progress
> updates.  I'm wondering if something similar to the 100-Continue
> mechanism could be used for this.

You can do this now by sending a single response with a multipart/replace
body.  All it costs is keeping a connection open.  The more general need is
for notifications that do not require an open connection, but that is a
different story.
Received on Thursday, 17 June 1999 17:19:58 EDT

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