wsrf message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsrf] Singleton Resource Pattern
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: "Steve Graham" <sggraham@us.ibm.com>
- Date: Mon, 12 Jul 2004 14:55:17 -0400
Then what value does the implied pattern add to the use
case I have included?
Why
does resource pattern have to depend on WS-Addressing, EPRs and customizations
of those?
Why
can't GetProperty/SetProperety be defined independently?
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza,
Islandia, NY 11788
>It seems that whether it
is an "implied resource" or an "implied singleton" has nothing to do with
GetResourceProperty (GetProperty for that sake) operation. In >other words
use of WS-Addressing does not add any semantic value to the fact that one could
retrieve a property by sending a message to a service.
Unfortunately, I disagree. The implied resource
pattern clarifies a certain pattern relating a web service and a stateful
resource. It is important that this pattern is clarified to allow a single web
service to act as the Web services message processor for a plurality of stateful
resources. Therefore the pattern of the message is formed to disambiguate which
of the potentially many stateful resources is associated with the message is
very important.
sgg
++++++++
Steve Graham
(919)254-0615 (T/L
444)
STSM, On Demand Architecture
Member, IBM Academy of
Technology
<Soli Deo Gloria/>
++++++++
| "Sedukhin, Igor S"
<Igor.Sedukhin@ca.com>
07/12/2004 11:56 AM
| To:
Steve Graham/Raleigh/IBM@IBMUS,
<wsrf@lists.oasis-open.org> cc:
Subject:
RE: [wsrf] Singleton Resource
Pattern |
Steve,
Your example was interesting. How about this one:
Web
Service implements a UserName property. Client sends a GetResourceProperty SOAP
message with WS-Security headers containing X.509 certificate. Web Service
returns the UserName after matching the certificate.
-- Is this a singleton or an implied resource pattern? One
could claim that there is a user resource, however this interaction does not use
WS-Addressing and moreover it would not be possible to build WS-RF qualified
EPRs for such interaction.
The same use case could be modified to include
UserDiskQuota property, and the same argument would apply.
It seems that
whether it is an "implied resource" or an "implied singleton" has nothing to do
with GetResourceProperty (GetProperty for that sake) operation. In other words
use of WS-Addressing does not add any semantic value to the fact that one could
retrieve a property by sending a message to a service.
-- Igor
Sedukhin .. (igor.sedukhin@ca.com)
--
(631)
342-4325 .. 1 CA Plaza, Islandia, NY 11788
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]