Paul Prescod wrote:

>  $foo->Ports  # list of ports
>  $foo->Port(...) # find a port by name and namespace
>  


FWIW, I tend to prefer verbNoun constructions. In this case that would be:

 >  $foo->listPorts()  # list of ports
 >  $foo->findPort(...) # find a port by name and namespace
 > 

Note how the comments become redundant.

This way, it's possible to add setPort, addPort, removePort without 
overloading Port in a potentially confusing manner. A standard 
vocabulary could be used for all WSDL sections (addMessage, findBinding, 
removeOperation).


>   2. ->Ports returns the ports in THIS WSDL. ->Port("...") finds a port
>  in any included or imported WSDL
>  


I'm not sure why this would be desired. Wouldn't a list of all ports in 
any included or imported WSDL be more useful?

A side question: is this going to use a nested-object model (like DOM, 
which would have $foo-> findBinding("bar")->findOperation("baz")) or a 
flat-object model (which would have $foo-> findOperation("bar", "baz"))? 
Forgive me if this is a stupid question or it's already been covered. I 
haven't been paying close attention. :)

Cheers,
~chris


_______________________________________________
Ws-dev mailing list
Ws-dev@[...].com
http://listserv.ActiveState.com/mailman/listinfo/ws-dev