- From: Mark Baker <distobj@acm.org>
- Date: Wed, 11 Jul 2001 10:23:12 -0400
- To: Mark Nottingham <mnot@akamai.com>
- CC: www-ws@w3.org
Mark Nottingham wrote: > > On Mon, Jul 09, 2001 at 03:58:13PM -0400, Mark Baker wrote: > > Mark Nottingham wrote: > > > It's not so much that as the decoupling of the request and response. > > > In other words, if they make a request, keep the persistent > > > connection open, and then send responses upon events, the 1->n > > > request/response relationship will confuse proxies. > > > > Confuse them any more than any other use of persistent connections? > > Hmm, what do you mean by 'other'? "Typical" use. If I understand you correctly though, you're concerned that a single GET may result in more than one "response". This presumes that a single event notification is a single response. I believe it's perfectly reasonable and consistent with the architecture of the Web to define a resource whose state is not expressible in a fixed size representation. That's what they're doing. This isn't to say that there isn't a better way of dealing with this, specifically the interaction with caching proxies, as it may still be of value to cache individual event notifications. I'm sure they'd welcome your input on that topic (and I wouldn't mind hearing it too 8-). Drop Rohit Khare (CTO) a line at rohit@knownow.com. MB
Received on Wednesday, 11 July 2001 10:23:18 UTC