- From: Amelia A. Lewis <alewis@tibco.com>
- Date: Wed, 30 Apr 2003 14:53:42 -0400
- To: "David Orchard" <dorchard@bea.com>
- Cc: gdaniels@macromedia.com, ryman@ca.ibm.com, www-ws-desc@w3.org
On Wed, 30 Apr 2003 11:47:32 -0700 "David Orchard" <dorchard@bea.com> wrote: > I'm having a bit of a tough time following this discussion. I get the > feeling that there are two competing requirements and pros/cons. Let > me know if this roughly the state of the discussion. > > 1. Amy: A web service has multiple ports for different semantic tasks > (such as notification and administration). These can be in the same > service. Pros: Software dealing with a somewhat complex MEP deals with > only one service. > Cons: Software can't determine what are the semantically equivalent > ports. Why not? port[1] -> binding[1] -> portType[1]. port[2] -> binding[2] -> portType[2]. If (portType[1] == portType[2]) the ports are semantically equivalent. This is the same as the check that would be performed to verify that all ports within a service implement the same portType, btw. Amy! -- Amelia A. Lewis Architect, TIBCO/Extensibility, Inc. alewis@tibco.com
Received on Wednesday, 30 April 2003 14:53:31 UTC