Access Controls

[linas@linas.org]

It's been rumoured that Tyson Dowd said:
> 
> On 02-Jan-2001, linas@linas.org <linas@linas.org> wrote:
> > Tyson,
> > 
> > Re: 
> > It's been rumoured that Christopher Browne said:
> > > CORBA Notification or Event services rather than changing GUIDs all the
> > > time.
> > 
> > 
> > We also have Derek Atkin's announcement that he has demo code working
> > that does event notification via onc-rpc.  Since soap/xml is our third
> > candidate for network services, does it have something analogous that
> > we're not aware of?  What's the recommended practice? Also, what
> > about Microsoft's .net?  Do they punt on this issue?  Are the .net
> > users SOL?
> 
> Ok, we are starting to reach the edge of my understanding of SOAP,

That's OK, the edge is a fun place to be.

> 	http://www.extreme.indiana.edu/soap/events/report.html
> 
> gives a sample of doing events with SOAP.

[...]

> SOAP/XML is (I think) completely orthogonal, 

Not quite; this goes back to the socket arguments we had earlier.

If the client uses HTTP, opens a socket to the server, sends 
an XML/SOAP message to the server, gets the servers reply, and closes
the socket ... Ooops, now there is no way for the server to send
out any events back to the client.   In order for the client to receive 
the events, it must have kept the socket open.   Thus the debate
about HTTP 'persistant connections' and whether Apache obeys that
directive, and whether firewalls mess it up.

Old versions of HTTP, and the generic Apache mind-set mostly revolves 
around the notion of 'deliver that payload, close the socket', which
is anti-thetical to the notion of keeping it open to listen for
events.  Which is why I asked. 

--linas