[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp-interfaces] State change in getMarkup?
One issue I would like to bring up again (maybe just as a clarification for me) is the ability of an entity to modify state in getMarkup. If I remember correctly be decided that an entity should not be able to modify conversational state in getMarkup, primarily for the reason that we want to be able to write a stateless consumer. Such a consumer would need to know all of the conversational state of all portlets on a page before it streams any markup to the client (because the consumer wants to encode the state in the URL). 1. What about the sessionID? Currently we allow getMarkup to return a sessionID. Wouln't a stateless consumer need to encode this ID also in the client URL? How could he do so if it might change in getMarkup? 2. JSR168 does not prevent portlets from modifying state in the service method (the getMarkup equivalent). How does this match with WSRP? Best regards Carsten Leue ------- Dr. Carsten Leue Dept.8288, IBM Laboratory B÷blingen , Germany Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401
Powered by eList eXpress LLC