MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [wsrp] [wsia] [wsrp-wsia joint interfaces] agenda for Tuesday 11June
Alan,
I too would like to not have the issue of whether or not an entity is
persistent stay within the Producer, but scenarios such as the one Eilon
points out have driven us toward a design where the Consumer is able to
create a persistent entity and then use this persistent entity as the basis
for creating a variable number of transient entities whose interaction
states are independent of each other, each often having a tweak in the
initial state as well. It is only the Consumer who has the knowledge of
when to orchestrate the difference in the lifecycles.
Rich
Eilon Reshef
<eilon.reshef@webc To: "'Alan Kropp'" <akropp@epicentric.com>,
ollage.com> wsia@lists.oasis-open.org, wsrp@lists.oasis-open.org
cc:
06/11/2002 02:35 Subject: RE: [wsrp] [wsia] [wsrp-wsia joint interfaces] agenda for
PM Tuesday 11 June
Alan,
I think that one example scenario is a search results page, say for hotels,
that dynamically displays multiple maps - a map for each hotel found.
Assuming that maps are remote services, and assuming that the number of
results is dynamic, the Consumer needs to create multiple copies of the map
service. If we allow the Producer to determine the persistence state of
those maps, that would mean that someone will have to take care of the
lifetime of those maps. The Consumer can't, because the page may be gone
without the Consumer never knowing about it (the user closes the browser
window). The Producer can't, because it can't tell whether the Consumer has
stored a reference to those maps as part of a design-time description of a
user page.
Is that along the lines of what you were looking for?
Eilon