[Seaside] Comet and #call:
andres at lifia.info.unlp.edu.ar
Thu Jul 29 21:04:19 UTC 2010
I forgot to mention, I'm running Seaside 2.8 in VW.
> 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
> When I do
> 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).
> 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.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside