I still need to do the adding context fix for this as well as upgrading scriptalicious.
On 3/10/06,
Andreas Andreou <[EMAIL PROTECTED]> wrote:
When autocompleter has direct=true,
only that component is rendered (by the PrototypeResponseBuilder), so
the ajaxresponse
was simply 24 bytes:
*<ul><li>*Greece*</li></ul>*
When autocompleter has direct=false, all components are rendered and we
just keep
the component output we want + all generated _javascript_ + hidden form
fields... That's
standard behaviour and it's how we get to do all those nice ajax forms +
ajax links and such.
However, I believe that this behaviour is only needed for
DojoResponseBuilder.
On the other hand, PrototypeResponseBuilder doesn't benefit from it. So,
I would like to
change PrototypeResponseBuilder's:
public IMarkupWriter getComponentWriter(String id)
to always return a NullWriter unless the ajaxRequest contains that
specific component id.
In other words, add the lines:
if (!ajaxRequest.containsComponentId(id))
return NullWriter.getSharedInstance();
, which BTW fixes bug70.
Or perhaps, this can be configurable (just like updateDirect is). It
would certainly help
cut down ajax-response length. And i've seen 12KB responses when the
real content is
only 10 bytes.
PS. The autocompleter example i mention above generates a 8.6KB response
with direct=false. With the patch it gets down to those 24 bytes again.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
