- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Tue, 22 Apr 2003 07:19:12 -0400
- To: "PRASANSR" <PRASANSR@infosys.com>, <www-ws-desc@w3.org>
This is a quality of service attribute and there are many of these: how long the service takes, how much it costs, etc. etc.. IMHO it doesn't make sense for a single standard to list all of these out its simply not possible. So what you need is a way to attach such characteristics to a service in various ways. WS-Policy* is about doing something like that .. as is some of the properties and features stuff we're doing and trying to sort out. Sanjiva. ----- Original Message ----- From: "PRASANSR" <PRASANSR@infosys.com> To: <www-ws-desc@w3.org> Sent: Tuesday, April 22, 2003 1:27 AM Subject: Expiry and Timeout Limits Hi, I am curios to find the reason why WSDL does not define expiry and timeouts limits for services as a standard. We have seen workaround implementations of sending this information over soap headers at call level. But this is something which is actually service specific. Although, one may want to override this at call level. With Best Regards, Prasanna S Raghavendra S prasansr@infosys.com ' +91 80 5117 5535
Received on Tuesday, 22 April 2003 07:48:00 UTC