Re: [wsia] [wsrp-interfaces] Another case for explicit session creation?

[Rex Brooks <rexb@starbourne.com>]

This makes good sense to me. I'm not so sure about passing the 
sessionID for all of a producer's entities rather than just the 
initial selection for that end user. Perhaps I am misunderstanding 
that last paragraph. Wouldn't that be a bit of curve for the 
Producer, and require reparsing the assortment of entities to be sure 
there isn't a new portlet being added to an existing session with 
each performInteraction? I can see where an end user might decide 
mid-session that an as-yet-unserved portlet is needed and request it, 
but I'm not sure if we want to get down to prescribing such things in 
this version.

I think experience might tell us better how this plays out.

Ciao,
Rex


At 9:06 AM -0700 8/7/02, Alan Kropp wrote:
>Not sure this went through the first time..
>
>-----Original Message-----
>From: Alan Kropp
>Sent: Tuesday, August 06, 2002 11:49 PM
>To: 'wsia@lists.oasis-open.org '; 'wsrp-interfaces@lists.oasis-open.org
>'
>Subject: [wsia] [wsrp-interfaces] Another case for explicit session
>creation?
>
>
>I'd like to open another thread for the explicit session creation question.
>
>In the standard portal situation, end users configure their own aggregate
>views or "pages" of the available portlet services.  When an end user first
>accesses their customized page, the portal needs to ask each of the portlets
>on the page to render their markup, assembles the page, and then presents it
>to the user.
>
>Consider for the sake of argument that a theoretical page is composed of
>five portlets, all of them remote portlets served by a single Producer.  The
>portal has already created and configured the necessary entities.
>
>In the portal startup case, the portal will send five individual requests to
>this Producer, each of them targetted at a different entity.  As there are
>no sessions in effect yet, the Producer in turn creates a session for each
>entity, and passes back the handle in the individual getMarkup response.
>
>It would be more efficient for the portal, however, if there was just one
>session created by the Producer, grouping all of the entities into a single
>session.  Otherwise, the portal must now map the end user's request scope,
>which in the standard http case is a single http session, to multiple
>Producer sessions, and it must be certain to put the correct session ID into
>the performInteraction/getMarkup for each entity. 
>
>The portal could explicitly request a Producer session ahead of any calls to
>getMarkup, and pass this sessionID to getMarkup for all of that Producer's
>entities.
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>


-- 
Rex Brooks
Starbourne Communications Design
1361-A Addison, Berkeley, CA 94702 *510-849-2309
http://www.starbourne.com * rexb@starbourne.com