Tomorrow's agenda

[Michael Freedman <michael.freedman@oracle.com>]

I have attached a document that lists 3 open discussion items from the 
wsrp list + the security topic.  I suggest we spend a little time on the 
open issues but also make sure we have enough time to begin the security 
discussion.  The topics have links to the mail threads so you can 
refamiliarize yourself.
    -Mike-

Title: WSRP Interfaces issues

navigationalParameterDescriptions:
Do we need to clarify language concerning consumers recognizing like-named navigational parameters as related/auto wired?

Clarification: Resource URLs and markup params, etc.

1. Stateless consumer
2. Meaning of title?
3. Change window state/mode?
4. Concurrency problems with sessionID?
5. During getMarkup, handleEvents and performBlockingInteraction invocations the Consumer indicates to the Portlet its current mode via the MarkupParams data structure"  Add getResource???
6. Clarity of structure vs reuse of structure -- Should we have specific types to clarify that a few fields are no sensible?
7. Caching when using getResource of portlet markup ???? Not yet raised ---

unclear behavior for dynamic nav params and transient properties
Why don't we allow nav params/transient props to be introduced dynamically like events?  Should we?

Security questions:
Can we recommend that all producers support at a minimum UserName with
no consumer authentication?  Can we encourage all consumer to send
UserName with no consumer auth unless otherwise instructed to do
otherwise?  Will a producer work if it doesn't handle the WS stuff
but receives it?  I.e. will it just be ignored?