Hello Mike;
I do have some thoughts on stateful JSON services, though, to move from the straight RPC route and towards a "component action" model of services. We'll see if it works out or just makes things more confusing :)
Although I have not yet encountered it in a commercial setting, there is the possibility that one would like to maintain state on the server- side in a session and aside from the session default EC. I think the need for this is somewhat reduced in a web services client because in many cases, the client is able to hold state, but I can still think of cases where holding all the state in the client would be either inefficient or impossible. Are you talking about this sort of situation?
I had thoughts about how my "navigation destination" (ND) architecture (discussed on Sat) with specific named endpoints might support those sorts of workflows from a web-services client. Essentially the HTML is replaced with a JSON-RPC client, the stateless component controller is replaced with a stateless JSON-RPC endpoint action and the state is stored in the ND stack.
I haven't done any work on this yet and there may be a different or better architecture for this -- so be interested in hear what approach you are taking in this area.
cheers. ___ Andrew Lindesay www.lindesay.co.nz _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
