RE: Allow: header and supported methods

No, you could do something like FTP does and have an HTTP
method that tells the server a port to connect to in order
to deliver invalidation responses, something like:

REG_NOTIFY /foo.txt HTTP/1.1
Host: www.oracle.com

<respond-to>
  <href>http://192.251.211.44:4234/notify</href>
</respond-to>

and the server would then post a list of HREFs to invalidate
to that address.

You just require that the client also be able to function
as a server.

The disadvantage of this approach is that is that it will
have problems with many firewalls.  The advantage is that
the server doesn't have to keep open a socket to the client
just in case an invalidation would have to be done.  The
server could end up with a very large number of sockets in
this case.

--Eric

> -----Original Message-----
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Jim Amsden
> Sent: Sunday, August 19, 2001 5:20 PM
> To: ietf-dav-versioning@w3.org
> Subject: Re: Allow: header and supported methods
> 
> 
> We'd have to introduce push technology into HTTP.
> 
> 
> 
> 
> 
> Peter Raymond <Peter.Raymond@merant.com>
> 08/19/2001 08:15 AM
> 
>  
>         To:     Jim Amsden <jamsden@us.ibm.com>
>         cc:     Eric.Sedlar@oracle.com
>         Subject:        Re: Allow: header and supported methods
> 
>  
> 
> Hi Jim,
> 
> Jim Amsden wrote:
> 
> > Anyone interested in a new WebDAV working group to add event 
> notification?
> > We could call it DAVE.
> 
> Sounds like fun and certainly something I would be interested in.
> 
> But, how would we do that over HTTP? Since the protocol is 
> request-response based the client
> would
> have to be polling at regular intervals asking if any events of interest 
> have occurred.
> Would this perform well?
> 
> Regards,
> Peter Raymond - MERANT.
> 
> 
> 
> 
>

Received on Monday, 20 August 2001 19:36:06 UTC