MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [wsia] The search for per-entity-per-user Consumer state
Gil - I think I missed your point.
May new attempt to answer the question: the client needs to store one
handle per entity per user (or to be more precise: a handle for each entity
users display on their pages).
Best regards
Carsten Leue
-------
Dr. Carsten Leue
Dept.8288, IBM Laboratory B�blingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
|---------+---------------------------->
| | Gil Tayar |
| | <Gil.Tayar@webcol|
| | lage.com> |
| | |
| | 06/18/2002 05:40 |
| | AM |
| | Please respond to|
| | Gil Tayar |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: Carsten Leue/Germany/IBM@IBMDE |
| cc: wsia@lists.oasis-open.org, wsrp@lists.oasis-open.org, "'Michael.Freedman@oracle.com'" <Michael.Freedman@oracle.com> |
| Subject: RE: [wsia] The search for per-entity-per-user Consumer state |
| |
| |
>---------------------------------------------------------------------------------------------------------------------------------------------|
Carsten,
Either I misunderstood your answer, or you may have missed the fact that I
was searching for _Consumer_ (not Producer) information that must be stored
per-entity-per-user.
Mike's concern about the OO-way of thinking - in which the basis is a
per-entity-per-user references - is that the Consumer will have too many of
these references.
What I was trying to say in this email is that the Consumer _must_ have
information that is per-entity-per-user _anyway_: because of the way
actions
work, and for stateless producer services, the Consumer must at least store
the last action of the producer service.
Gil