Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:COSMOS Design 197870
Revision as of 09:11, 13 August 2007 by Unnamed Poltroon (Talk) (New page: [Joel's comments] Client API * provide an alternate implementations of get that takes an EndpointReference. * Why do many of the 'factory' methods return WsResourceClient? Why not an ext...)
[Joel's comments] Client API
- provide an alternate implementations of get that takes an EndpointReference.
- Why do many of the 'factory' methods return WsResourceClient? Why not an extentsion of WsRescourceClient (like DataBrokerClient)?
- Why are all of the instance-oriented methods static? Making these static and limiting ourselves to WsResourceClient makes it hard to expose session-oriented information later on. I'd vote for creating client classes that extend WsResourceClient, and have the static 'get' methods return instances of these classes. That way, if the static 'get' method wants to implement singleton semantics, it can easily do so without painting the extender of these client API into a corner.