RE: [wsrp-wsia] [change request #155]

[Richard Jacob <richard.jacob@de.ibm.com>]

Isn't that already a cache if you send it with the first render and then
you don't? (And in fact we don't define its behaviour)
Yes, I assumed that we mean the complete userContext and thus the
userProfile also. Didn't we introduce this flag to save the amount of data
that goes over the wire?
Also we state that the user context may be send on any invocation, which
one could interpret as anytime when one calls an operation that takes
userContext as a parameter.
Therefor I would say it's not only the first render.
My concern is that we haven't a clear semantics defined yet and that we
should do this.
What is the portlet supposed to do when it keeps the userContext in the
session and receives it also with an invocation as parameter?
Which one wins?
If the one passed with the request wins, doesn't the portlet need to update
the one stored in its session?
If not then we say: use the first one passed and store it in the session,
whenever a fresh one comes in use this, don't care about the one in the
session.
If the one in the session wins, the Consumer needs to pass the userContext
again once the session times out (and we don't say that). Why should the
consumer be allowed to resend them in this case, it's useless?

If a portlet is stateless it simply doesn't set the flag, right?
The partial question is also a good one. I would assume that a userContext
passed in an invocation simply completly replaces the one stored in the
session. I wouldn't like to deal with partial updates.

So bottom line: I wouldn't deal with partial updates. In general I could
imagine to go either symantics discussed. But my concern is that it isn't
defined very well right now.

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


|---------+---------------------------->
|         |           "Kropp, Alan"    |
|         |           <Alan.Kropp@vigne|
|         |           tte.com>         |
|         |                            |
|         |           02/25/2003 08:52 |
|         |           PM               |
|---------+---------------------------->
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                                                  |
  |       To:       "'wsrp-wsia@lists.oasis-open.org'" <wsrp-wsia@lists.oasis-open.org>                                                              |
  |       cc:                                                                                                                                        |
  |       Subject:  RE:  [wsrp-wsia] [change request #155]                                                                                           |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





Is this giving the impression that the portlet is supposed to maintain a
"cache" of UserContext (profile too?) data, that gets updated during the
session by the Consumer?  It sounds useful, but it also sounds like
something we don't want to consider for 1.0.  The "full" user context gets
conveyed to the portlet upon initial render, right?  So worst case, the
changed profile data doesn't get reflected until the next time the user
initiates a session with this portlet.

What about stateless portlets?  How would they be expected to handle
partial
UserContext?

Alan


-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Wednesday, February 19, 2003 8:03 AM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #155]


Document: Spec
Section: 5.1.11
Page/Line: 20 / 29
Requested by: Richard Jacob
Old text: Note that the Consumer MAY send UserContext information on any
invocations regardless of the value of this flag.
Proposed text: Note that the Consumer MAY send UserContext information on
any invocations as an update of any information the Portlet MAY be storing
in a session.
Reasoning: Clearer semantics for when there is data in the session AND in
the invocation. Same change for templatesStoredInSession.

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>