[Seaside] Re: Re: #with: and #children: is one redundant?

itsme213 itsme213 at hotmail.com
Sat Oct 20 14:55:13 UTC 2007

Ah, I get it. Thanks Lukas and Avi. I was just hoping to DRY it a bit more.

"Avi Bryant" <avi at dabbledb.com> wrote in message 
news:3c71d5330710191108g7db98b37sea2b352db37d8fda at mail.gmail.com...
> On 10/19/07, Lukas Renggli <renggli at gmail.com> wrote:
>> For example, if you want your visible components to be able to add
>> elements to the <head>, then you need to call their #updateRoot:
>> method before you let them generate the <body>. At the time the <body>
>> is rendered the <head> might already have left the server and is on
>> the way to the client (when using a streaming server at least).
> And there's a redirect between #children being asked to #updateUrl:,
> and being rendered to the <body> - so it's not just in the streaming
> server case that it matters.
> Another count against a null rendering pass is that in many cases this
> would double the response time, since all database queries etc would
> get (needlessly) executed twice.
> Avi 

More information about the seaside mailing list