- From: Joseph Hui <jhui@digisle.net>
- Date: Thu, 2 May 2002 17:50:04 -0700
- To: "Hugo Haas" <hugo@w3.org>, <www-ws-arch@w3.org>
> -----Original Message----- > From: Hugo Haas [mailto:hugo@w3.org] > Sent: Thursday, May 02, 2002 12:23 PM > To: www-ws-arch@w3.org > Subject: D-AR006.11: Communication with the underlying infrastructure > > > D-AR006.11 reads: > > + D-AR006.11 The architecture must provide an > interface for Web > Services to directly communicate with their underlying > infrastructure. > The interface is for negotiating services that an > infrastructure may provide to, or perform on behalf of, a > requesting Web Services. Such value-added services may > include: security, content delivery, QoS, etc. > For instance, > a Web service may instruct (via the interface) > the security > agents of its infrastructure to defend against DOS/DDOS > attacks on its behalf. > > This seems implementation-dependent, i.e. out of scope for us. Not necessarily. What's imp-dependent can be made imp-independent. That's what standards are all about. But don't matter, imp-dep and in/out-of-scope are apple and orange anyway. To the WG, the issue is whether it should be in or out of scope. Cheers, Joe Hui Exodus, a Cable & Wireless service
Received on Thursday, 2 May 2002 20:50:40 UTC