wsrf message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [wsrf] Singleton Resource Pattern
- From: Ian Robinson <ian_robinson@uk.ibm.com>
- To: John Fuller <jfuller@wernervas.com>
- Date: Tue, 13 Jul 2004 09:33:43 +0100
See previous discussion of WS-Context and WSRF:
http://www.oasis-open.org/archives/wsrf/200405/msg00087.html
Regards,
Ian Robinson
STSM, WebSphere Transactions Architect
IBM Hursley Lab, UK
ian_robinson@uk.ibm.com
| John Fuller <jfuller@wernervas.com>
12/07/2004 20:46
|
To: Rich Thompson <richt2@us.ibm.com>
cc: wsrf@lists.oasis-open.org
Subject: Re: [wsrf] Singleton Resource Pattern
|
Could WS-Context from WS-CAF help for these situations?
On Jul 12, 2004, at 2:40 PM, Rich Thompson wrote:
>
> But with the stateless character of web services, that UserName
> property would be shared by all users of the web service. There may be
> some usefulness to that, but it becomes far more useful when the web
> service interface fronts access to a multiplicity of state, each
> storing such a property.
>
> To make this a concrete example, presume the UserName property is
> really a reference to a field in a database. One could provide a
> separate web service interface for each record within the database,
> but it would be a much lighter (and frequently more useful) definition
> if there was a single web service interface that had some well defined
> means for indicating what record of the database was the target of the
> current invocation. WSRP had this type of need and had to define a
> means that is idiosyncratic to our protocol for passing the stateful
> reference. Defining a standardized means by which infrastructure can
> take more of the load for handling such references is one of the
> outcomes I would like to see from the WSRF effort.
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]