RE: [provision] Session context token?

Agree - This could be very useful for further clarification of the
provider-side resource management mechanisms we described in the
resource considerations paragraph in section 3.5.7 (Search Capability).
Since a session context will provide a timeout value, this could be used
by the provider to destroy any unused resources associated with the
session / requestor.

Martin

-----Original Message-----
From: Gary P Cole [mailto:] 
Sent: Montag, 27. Juni 2005 19:55
To: Jeff Bohren
Cc: PSTC
Subject: [provision] Session context token?

Jeff,

Kent Spaulding, the developer working on Sun's SPML2 implementation for 
the Interop, points out that our previous provider implementation 
returns an opaque token (in our case, a "sessionID") that represents the

logical session (or perhaps session context).  If the requestor passes 
this token as part of subsequent requests, it saves a great deal of 
processing on the provider's side.  It may also assist with audit 
logging, which you've indicated you expect will become important.

I believe that this feature (i.e., an opaque and optional session 
context element returned by the provider and passed by the requestor as 
part of subsequent requests) may be important enough and general enough 
to recognize as part of the specification.  I'd like to know what other 
members and participants think.

Would you be willing to consider this issue?

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php