RE: Visibility (was Re: Introducing the Service Oriented Architec tural style, and it's constraints and properties.
"David Orchard" <[email protected]> Wed, 26 Feb 2003 10:14:37 -0800
| Newsgroups | gmane.comp.web.services.ws-arch |
|---|---|
| Message-ID | <[email protected]> |
Imagine that an intermediary that has to deal with multiple protocols. So it has to be configured with understanding multi-protocols. In the same way there are "HTTP Routers" that understand 1 protocol, "SOAP Routers" understand many protocols that SOAP is layered upon. Cheers, Dave > -----Original Message----- > From: Mark Baker [mailto:[email protected]] > Sent: Tuesday, February 25, 2003 9:50 PM > To: David Orchard > Cc: [email protected] > Subject: Re: Visibility (was Re: Introducing the Service Oriented > Architec tural style, and it's constraints and properties. > > > On Tue, Feb 25, 2003 at 10:41:05AM -0800, David Orchard wrote: > > Visibility may or may not be improved. For single > protocols, visibility is > > improved with use of GET, PUT, DELETE - not POST as Chris > Ferris explained. > > But for multi-protocol, visibility may be improved by other means. > > I'm sorry, but I don't understand what that means. > > What do you mean by single vs. multi protocols? > > MB > -- > Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca > Web architecture consulting, technical reports, evaluation & analysis >