[Seaside] Comet and #call:

Julian Fitzell jfitzell at gmail.com
Thu Jul 29 23:21:44 UTC 2010

That's because the Render Loop, after processing callbacks, then
returns the rendered page as the response. If you want to return
something else, either you don't want to be using the Render Loop, or
you need to manually return a response in the callback (in 2.8: "self
session returnResponse: ..."

On Thu, Jul 29, 2010 at 10:01 PM, andres <andres at lifia.info.unlp.edu.ar> wrote:
> I guess I must be missing something because I see no difference between
> #call: and #show:, except for the fact that #call blocks and #show does not.
> When I do
> MyApp>>...
>        self
>            update: #componentPane
>            with: Component1 new.
> The network traces in firebug shows that only the required resources for
> Component1 are requested to the server. On the other hand when I hit the
> link rendered by:
> Component1>>renderContentOn: hmtl
>            html anchor
>                    callback: [self show: Component2 new];
>                    with: 'A call'.
> firebug shows that everything that belongs to the page is requested again to
> the server (all the .css, .js, etc).
> Thanks,
> Andrés
> Lukas Renggli escribió:
>>> code in WAComponent>>call: without any luck :(. So, do you think this can
>>> be
>>> done? Am I missing something important about the way Seaside works? Any
>>> hints are very much appreciated!
>> Did you look at #show:/#show:onAnswer:? This is the #call:/#answer:
>> without continuations and without the forced full-page refresh.
>> Lukas
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list