Slides on 2'0 Feature Proposals

1
Slides on 2.0 Feature Proposals

• Andre Kramer, Citrix Systems Inc.

2
Resources (1)

• 1.0 Status Quo
• Markup over SOAP Resources (e.g. Images) over
  HTTP
• Problems
• HTTP may need to be proxied by consumer (1.0 spec
  is extreemly complex here)
• Developers have to use a different tool chain
• L7 Firewalls may wish to control all related
  traffic
• Cookies should not need to be required
• Solution?
• Eat own dog food
• Assume efficient binary attachment mechanism -(
• Previously proposed new getResource operation
• Very similar to getMarkup
• Called outside of 1.0 Two-step protocol
• ResourceID (URI) as resource parameter
• Requires new URL type (and updated re-writing
  rules)

3
Resources (2)

• Suggested new approach
• Start with getMarkup() and render URLs
• Relax when/how interactions can be initiated
• ltimage/gt tags, ECMAScript
• TODO
• Examine each getMarkup parameter
• Is it sensible/required for resources?
• Is optional/required ok?
• Factor in resourceID parameter
• Possible disadvantages
• Overloading is Bad
• Are resources per-Portlet or per-Producer?
• Cache control required?
• Now we need invalidation caching -)
• Why not wait for WS Resource Framework?
• Or SOAP 1.2 support for REST?

4
Leasing (1)

• 1.0 leaks Resources
• Unreliable end-to-end transport implies clones
  etc may be done but not recorded by Consumer
• Fly-by-night Consumers come and go
• How many times should I try destroyPortlets()?
• Proposal
• Leasing for Portlet handles and Registrations
• Soft-state for Sessions
• Look at OASIS WS Resource Framework TC work

5
Leasing (2)

• WS-ResourceLifetime 1.2
• Working Draft 03, 10 June 2004
• 31 pages!
• Supports Destroy
• Only for Resources
• ltwsrlDestroy/gtltwsrlDestroyResponse/gt
• Leasing supported by TerminationTime
• Is a resource Property, modifyable by
• ltwsrlSetTerminationTime/gt carries xsddateTime
• ltwsrlSetTerminationTimeResponse/gt
• Carries wsrlNewTerminationTime (and CurrentTime)
• Other
• Resource termination notifications
• Security concerns

6
Leasing (3)

• Options
• Adopt WS-Resource Framework for WSRP X.0
• Link interfaces, e.g.
• Make handles ltEndpointReferences/gt
• Allow casting such handles to WS-Resources
• Copy the functionality into our interfaces
• Re-invent more state management
• Dont do it