[Seaside] Form, serialize:, answer: and callback:
johan at inceptive.be
Wed Jun 12 07:15:26 UTC 2013
On 12 Jun 2013, at 08:24, intrader <intrader at aol.com> wrote:
> It is unclear to Dan that callback does a full page refresh. Please let me
> know as I am not entirely clear, and it is possible to play with priorities
> to cause callback to behave differently.
callback priorities only determine the order of execution of callbacks when several callbacks are being serialized over a single http call.
As an application programmer, you should almost never have to deal with them. They are, in fact, hard-coded in the WACallback classes.
The mechanism of call: and answer:  operates only in the context of regular callbacks. In essence, they only meaningfully execute in the context of a regular (full page) callback.
Hope this helps,
More information about the seaside