Re: [Tacos-devel] direct parameter

[Michael Waluk]

Hi,

 

It seems like DojoResponseBuilder's updateComponentsDirect method could be changed to avoid calling render on unecessary components (it is doing so with the NullWriter now).  For example, if checkComponentContainers would return null for components that don't have PartialForBean containers it should work.  I understand changes in Tapestry would be the ideal, but I'd hate to wait for v5 for this.  We're using DWR (and our own DHTML) right now when we need this sort of thing, but I'd love to satisfy all our ajax needs with tacos alone.

 

Another (less important) question:  Without direct="true" working I had some lamer ideas like putting my component on a 2nd page and either call its listener on that page (therefore the page refresh only rendered the 1 component) or call the listener on the original page but use cycle.activate() to forward to the new 2nd page for rendering the response (even goofier).  I looked at AjaxDirectServiceImpl and was wondering why the "checkNewPageActivated" method treats a forward like a redirect? 

 

Thanks,

Michael

On 2/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:

Yes this issue has been thought about a great deal. It ~might~ happen in tapestry4.1, will definitely happen in tapestry5. I don't know which yet.
 

jesse

On 2/23/06, Jonathan Bullkich <[EMAIL PROTECTED] > wrote:

Hi,

 

I'm working with tacos4-beta-1 and I'd like to know some details about the status of the direct parameter:

Right now it's not implemented, all components except the AjaxDirectLink ignore it,

also, there's a TODO comment in DojoResponseBuilder to handle the order in which components

are rendered.

Are there any plans to implement it?

 

Another thing, the way that it's implemented right now, even when the direct parameter is true,

the rendering is performed for every component, with the NullWriter, but still, all the server

side work, to get each component value is performed.

I'd really like that when the direct parameter is true, that only the components in the updateComponents

List will perform their server side logic.

Have you thought about this issue?

 

Thanks,

 

Jonathan