OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [wsia][wsrp-interfaces] Is sessionID transparent to the Consu mer?

I believe they should be distinct.

Let's take a normal web application, and we'll use one which _is_ "session-stateful", i.e. has a session. In most cases, this application will not only store things in the session, it will also continue to store things in the URL. Why? Because the information in the URL is (to coin a phrase) "bookmarkable", i.e. the user expects that if it bookmars the page, it will return to it when using the bookmark. In session-based applications, this may happen after a "re-login", but if enough information is stored in the URL, it will happen. If the app had stored everything in the session, it would not have supported this.

To sum it up, a stateful application stores its state both in the URL and in the session. The URL state is usually "bookmarkable" (or "navigation") state, while the session state isn't.

Going back to WSIA/WSRP, the Producer must _hint_ to the Consumer what state is which type, and thus the separation between markupParams and sessionID. The Producer _expects_ the Consumer to store the markupParams in its URL and the sessionID in its session. This is only a suggestion, because of course the Consumer CAN do whatever it wants.

Maybe markupParams should thus be called "interactionParams" (or "interactionState") because it stores navigation/interaction state, and thus its difference from session would be more clear.

-----Original Message-----
From: Rich Thompson [
Sent: Mon, July 15, 2002 20:53
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: [wsia][wsrp-interfaces] Is sessionID transparent to the

Having the sessionID be transparent originally was to allow the Consumer to
indicate when a Producer could reclaim the related resources. As was
mentioned in a side conversation at the face-to-face, other references
within the markupParams may also want such an indication. Any other reason
to keep sessionID as a separate data item?

                      "Tamari, Yossi"                                                                              
                      <yossi.tamari@sap        To:       wsia@lists.oasis-open.org,                                
                      .com>                     wsrp-interfaces@lists.oasis-open.org                               
                      07/15/2002 12:47         Subject:  RE: [wsia][wsrp-interfaces] Refactoring the data objects  

See my comments marked with [YT].
(Most of them are in appendix A, since it seems appendix a is the real
definition of the spec, which I think is wrong, and is a result of what
Rich mentioned below about the obscurity of the interface.)

The endless debate about putting WSIA concepts in the WSRP standard is
still there...


-----Original Message-----
From: Rich Thompson [
Sent: Friday, July 12, 2002 9:09 PM
To: wsia@lists.oasis-open.org; wsrp-interfaces@lists.oasis-open.org
Subject: [wsia][wsrp-interfaces] Refactoring the data objects

As requested in Tuesday's Joint interfaces call, I have reworked the draft
spec in an effort to factor the data items into the scopes presented at the
June F2F. Personally I think this obscures too much and that some of the
data items should move up to first class parameters in the interface.
Hopefully this version can provide a reasonable basis for a discussion of
which items should be promoted either for clarity or as part of supporting
any factoring of the operations.

Technical note: In order to make this readable but yet leave an indication
of what was modified, I accepted the changes and then appended a space on
the end of changed lines so that a change bar will appear on the left. So
much changed in Appendix A that it all should be considered modified.

(See attached file: WSIA - WSRP Interface Specification.doc)

#### WSIA - WSRP Interface Specification1.doc has been removed from this
note on July 15 2002 by Rich Thompson

To subscribe or unsubscribe from this elist use the subscription
manager: <

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC