I can't, but I would imagine it would offer much of the same elements of a distributed component (like a CORBA service) document. Which broadens the scope of examples.
One suggestion - whether you are just writing a client, or just exposing a service - you should obtain detailed performance requirements. What number of concurrent calls should be supported (if any), and timing thresholds for calls (peak load maximum average call time). We obtain that by estimating the volume of calls (sometimes pretty easy to do in our industry/situation, examine how that is distributed over 24 hours - is it focused on business hours for example, and work back to calls per second). Peter -----Original Message----- From: Dave Searle [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:52 PM To: [EMAIL PROTECTED] Subject: Web Service Requirements Hi All, Can any one point me to a requirements document for a typical Web Service? Kind regards, Dave Searle. **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************
