I
think the best guidance we can provide is to ignore this case, implicitly saying
that we do not think it should be used...
I
agree that the _applications_ behind the portlets maybe receiving and sending
OOB events, but I do not think portlets should do that. Portlets have a very
clear life cycle, and in my view when they are not explicitly called by the
container (and consumer) they should be dormant (in a sense they only exist
during the request cycle. Between requests it's just their state that persists,
just like servlets, ASP pages, etc.).
Yossi.
-----Original Message-----
From: Rich Thompson
[mailto:]
Sent: Monday, August 04, 2003 7:28
PM
To:
Subject: Re:
[wsrp-coord] Should we design in support for out-of band
events?
This is
equivalent to saying that it is up to each implementation to decide how
out-of-band items get reflected into the WSRP interactions. My gut instinct
says this is where we will likely end up, but I think we would do a disservice
to the community-at-large if we don't at least consider the implications
related to out-of-band events and possibly provide some guidance.
Rich Thompson
Alejandro Abdelnur
<>
Sent by:
08/04/2003 11:48 AM
To:
Rich Thompson/Watson/IBM@IBMUS
cc:
Alejandro Abdelnur <>,
Subject:
Re: [wsrp-coord] Should we design in support for out-of band
events?
I'm not sure
we should we care about out-of-band events, unless we
consider pushing
them through WSRP calls. In other words, making them
in-band.
Alejandro
On Monday, August 4, 2003, at 06:19
AM, Rich Thompson wrote:
>
> I think it is important
when considering this question to start with
> the realization that
out-of-band events will occur. We need to
> consider how to reflect
these into the interactions between the WSRP
> actors (Portlet,
Producer, Consumer and End-User) when out-of-band
> communication
between at least some of these actors is not in place.
>
> To
consider:
> 1. Portlet/Producer receives an out-of-band event that may
cause a
> change in its state.
> 2. Consumer receives an
out-of-band event (i.e. not a user
> interaction) that it wishes to
distribute to various Portlets. Does
> distributing coordination info
(events or state) always result in the
> aggregation of markup?
>
3. User-agent receives an event. Is any communication arising from in
>
this case just a virtual user-interaction (i.e. the other WSRP actors
>
view it as a user-interaction)?
>
> Rich Thompson
