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
The search service is implemented on the Consumer in this scenario. The
Consumer is choosing to place a map relative to each record in its search
results. In general it is the generation of a dynamic page where an entity
is used in the dynamic portion of the page.
Alan Kropp
<akropp@epicentri To: "'Eilon Reshef'" <eilon.reshef@webcollage.com>, Alan Kropp
c.com> <akropp@epicentric.com>, wsia@lists.oasis-open.org,
wsrp@lists.oasis-open.org
06/11/2002 03:04 cc:
PM Subject: RE: [wsrp] [wsia] [wsrp-wsia joint interfaces] agenda for
Tuesday 11 June
Hi Eilon,
It seems to me the Consumer still doesn't really need a say in how the
Producer implements the search service runtime model. It's true that if
the Producer creates all of these transient entities, there is the issue of
when it is "safe" to destroy them. Transient entities don't have an
inherent lifecycle, but the sessions which talk to them do...so, when these
sessions have timed out, the Producer is able to determine that a transient
entity is no longer a party to any active session. Would it be valid to
say that the Producer, at that point, may assume the transient entity is
stale and destroy it? I guess this is a variation on reference counting/GC
that Java developers are already familiar with.
I don't think it's unrealistic to expect the Producer to employ
intelligence like this to efficiently manage its entities.
Alan