are you trying to inherit from a stateless component ?

it's true stateless have less overhead and for small things, they are great - 
but of curse, some components need to be synchronized by design.

so, it might be best to read up on the subjects relating to the differences 
between stateless and stateful.

perhaps others have something more like advice about it or transitioning toward 
more of it.




On Aug 21, 2012, at 2:19 PM, WebObjects TORAcom <[email protected]> wrote:

> Hi List,
> 
> I am trying to implement best practices in our applications, we want to take 
> control of component's  binding syncrhonization.
> 
> First of all I understand that we should override the 
> synchronizesVariablesWithBindings function like this:
> 
> 
> public boolean synchronizesVariablesWithBindings() {
>               return false;
>       }
> 
> 
> 
> But where in the request - response loop should be the better place to 
> synchronize our bindings, a lot of time ago (years) somewhere in the internet 
> I found info that recommends Pull binding's values in the 
> takeValuesFromRequest(WORequest r, WOContext c) method and Push binding's 
> values in the appendToResponse(WOResponse r, WOContext c).
> 
> I am not sure about that, so we have been working with the automatic 
> synchronization of our bindings.
> 
> 
> Thanks in advance.
> 
> Miguel Torres.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to