- From: Mark Baker <distobj@acm.org>
- Date: Tue, 28 May 2002 07:40:53 -0400
- To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
- Cc: www-ws-arch@w3.org
On Mon, May 27, 2002 at 10:58:36PM -0400, Champion, Mike wrote: > OK, what requirements and usage scenarios are not met when SOAP > is treated as the application protocol, and HTTP is a transport > protocol rather than an application protocol? Off the top of my head; - inability to reuse established agreement that permits a priori communication - inability to work over firewalls in the long run - inability to properly leverage the value-add of intermediaries developed for that application protocol (such as firewalls) It is a complete non-starter for an Internet scale architecture to do what you and David are suggesting. On the other hand, if you only want Web services to work behind the firewall, then this would be the easiest way to ensure that, because there's no pesky trust boundaries to worry about - i.e. you can safely assume a single administrator; http://java.sun.com/people/jag/Fallacies.html MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. distobj@acm.org http://www.markbaker.ca http://www.idokorro.com
Received on Tuesday, 28 May 2002 07:32:04 UTC