Re: targetResource wording

Sergey,

I think there is also a practical implication. In the case that two 
services implement the same interface AND have the same target resource, 
then they are alternatives. The client can pick the service that offers 
the most appropriate binding or endpoint.

Arthur Ryman





"Sergey Beryozkin" <sberyozkin@zandar.com>
Sent by: www-ws-desc-request@w3.org
06/20/2003 08:19 AM

 
        To:     "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, <www-ws-desc@w3.org>
        cc: 
        Subject:        Re: targetResource wording

 


Sorry for asking what likely is a trivial question, but :

> > Can a client processing service d1 and d2 descriptions to avail of 
this
> > targetResource attribute in any way ?
>
> Sure- to realize that d1 and d2 both have something on common: they
> are both services that mess around with the same resource.
So, for example,  a client sees a printer service which can print a 
document
to a printer (identified by a targetResource), and also sees a printer
management service which can manage the same targetResource.
I can't see at the moment how the client can utilize this information. 
Say,
a client now can set up a printer first before sending a document to print 
?
But wouldn't a client be able to do the same if there were  two services
descriptions available (printer and printer manager) but without a
@targetResource ?

Thanks !
Sergey Beryozkin