|
|
William Cox |
BEA |
|
|
Graeme Riddell |
Bowstreet |
|
|
Srinivas Vadhri |
Commerce One |
|
Y |
Monica Martin |
Drake Certivo |
|
Y |
Alan Kropp |
Epicentric (chair) |
|
Y |
Charles Wiecha |
IBM |
|
Y |
Rich Thompson |
IBM |
|
Y |
Carsten Leue |
IBM |
|
Y |
Thomas Schaeck |
IBM |
|
Y |
Rex Brooks |
Individual |
|
Y |
Joe Rudnicki |
Navy |
|
Y |
Mike Freedman |
Oracle |
|
|
Stefan Beck |
SAP |
|
Y |
Jeffrey C. Broberg |
Silverstream |
|
|
Suresh Damodaran |
Sterling Commerce |
|
|
Eilon Reshef |
WebCollage |
|
Y |
Gil Tayar |
WebCollage |
|
Y |
Steve Pruett |
Silverstream |
|
|
Mike Hillerman |
|
|
Y |
Aditi Karandikar |
France Telecom |
Persistent data = data that the Consumer needs to create an entity.
Transient data = data applicable to the ongoing interaction with a Consumer of the service (conversational state). A Producer is interested in End User-related and backend related transient (e.g., database connections) data.
MF: Two scopes for transient data: Consumer, End User.
GT: How would portal know what transient data should be shared with which portlets?
MF: Portlet container is a group of portlet entities for purposes of sharing transient state.
RT: Additional levels of scoping should be allowed: Application-level, Container-level, End-User-level, etc.
CL: Depending on how some data is scoped, it may not require a wire representation (i.e., application-level).
1.) Portlets that share information not running in the same VM.
2.) Producer receiving notification of changes in the transient state.
MM: Is security information part of the interaction between Producer and Consumer?
RT: Yes. Needs additional fleshing out, “policy” discussions in the security sub-group.
Configuration at the service level, possible to handle via URL patterns. This would permit multi-level data hierarchy based on the extended URL.