Hello Quinton;
Yes, I had imagined that. Do you think the responsibility for
creating the context in the action is significant?
I'm working on some architectural-level changes to my JSON-RPC system
and so I'm just wondering if this is an arbitrary decision or there is
some significance? The 'handleActionRequestError' method is taking a
WORequest and no WOContext. I get Lachlan's point as well, but the
context is actively accessible in the WOAction and as you say it is
not lazily created. Maybe the anticipation was that at some later
point in time that it would be _possible_ to lazily create it if the
constructor took WORequest.
cheers.
Out of design curiosity; can anybody tell me why WOAction
constructor is taking a WORequest rather than a WOContext?
Because the context doesn't exist yet, it gets created by the
WOAction constructor.
___
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]
