12 messages in org.oasis-open.lists.wsrp-commentRe: [wsrp-comment] Comment on Today's...| From | Sent On | Attachments |
|---|---|---|
| Rex Brooks | Jun 11, 2002 10:33 am | |
| Michael Freedman | Jun 11, 2002 11:14 am | |
| Rex Brooks | Jun 11, 2002 11:23 am | |
| Rich Thompson | Jun 11, 2002 1:01 pm | |
| Michael Freedman | Jun 11, 2002 1:21 pm | |
| Rich Thompson | Jun 11, 2002 1:37 pm | |
| Rex Brooks | Jun 11, 2002 2:03 pm | |
| Eilon Reshef | Jun 11, 2002 2:21 pm | |
| Michael Freedman | Jun 11, 2002 2:29 pm | |
| Michael Freedman | Jun 11, 2002 2:37 pm | |
| Rex Brooks | Jun 11, 2002 3:05 pm | |
| Michael Freedman | Jun 11, 2002 4:24 pm |
| Subject: | Re: [wsrp-comment] Comment on Today's Joint Interfaces Working Telecon | |
|---|---|---|
| From: | Rex Brooks (re...@starbourne.com) | |
| Date: | Jun 11, 2002 11:23:17 am | |
| List: | org.oasis-open.lists.wsrp-comment | |
Thanks, Mike,
I wanted to be sure of this since we are scheduled to work on the glossary tomorrow, and I would like to capture at least as much as we managed to reach consensus on.
Rex
At 11:11 AM -0700 6/11/02, Michael Freedman wrote:
I think you mostly got it. The key mistake (if I understand your e-mail) is that the client/consumer session is equivalent to the sessionID in the API. The client/consumer session is of no concern to the API as its something between the client and the consumer vs. the consumer and the producer. Yes, its likely that a consumer will tie its session conversation with a particular producer to live within this client/consumer scope but it need not. -Mike-
Rex Brooks wrote:
Hi Everyone,
Unless I had cotton in my ears, I think we neared consensus on what a Session is for the purposes of having a sessionID for the interface. Correct me please if I am wrong, but I believe we arrived at a point where we can say that what we mean by Session is the conversation started by one end-user requesting service from one consumer, such that a sessionID is created by the consumer whose responsibility it is to manage this session/conversation with the end-user, providing for delivery of service from one or more producers.
There was also a related concept put forward for consideration called a sharedSession. This concept had many possible configurations, but the basic idea was that something like this was needed, in addition to transientEntities for economical management of multiple portlets within containers, multiple producers within a session, etc.
TransientEntities and sharedSessions were not quite narrowed down enough for consensus to emerge, and I may be mistaken about sessionID, but we certainly worked tenaciously at the interface issues.
Thanks, Rex --
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
--