- From: Mark Baker <distobj@acm.org>
- Date: Sun, 5 Jan 2003 15:29:06 -0500
- To: "Newcomer, Eric" <Eric.Newcomer@iona.com>
- Cc: www-ws-arch@w3.org
On Sun, Jan 05, 2003 at 02:45:34PM -0500, Newcomer, Eric wrote: > So I'll just try once more to rephrase in the hopes of being more understandable than precise: people do compare HTTP and IIOP despite the fact that they are, technically speaking, defined at different levels of the stack. And they do so because what we are trying to accomplish is the same, or similar enough, to warrant comparison. Okay, without the OSI-speak, with an example ... Imagine opening an IIOP connection to a remote, untrusted server. What method's can you invoke at that point? Now imagine opening an HTTP connection to the same remote, untrusted server. What methods can you invoke then? That's the difference between transport and transfer, and between layer 6 and layer 7. > Actually, by your logic, the comparsion of REST to Web services doesn't make sense, either, as they also are defined at different levels of the stack. Hmm, no, REST isn't a protocol, it's an architectural style. But if you mean that Web services doesn't specify any methods (i.e. does not define a coordination language), whereas REST does, then I agree. MB -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Web architecture consulting, technical reports, evaluation & analysis
Received on Sunday, 5 January 2003 15:28:48 UTC