Hello jsf-extenders,
In Jacob's JavaOne demo, he had an AsyncResponse class, available via
ThreadLocal storage, that was used for the following:
* vending the ClientWriter for this run thru the lifecycle
* vending a Map of client ids to "rendered markup" for any components to
be rendered to the AJAX response. This map is used by the
FaceletFilter to actually write out the XML response in a markup
understandable by the avatar JS file.
* Capturing the view state that is also sent in the XML to the browser.
I don't have such a class in my avatar impl. I don't buffer the
content. I intersperse the XML between calls to the components for
rendering. Jacob, why did you find it necessary to buffer?
Do you think we really need the AsyncResponse concept?
Ed
--
| ed.burns_at_sun.com | {home: 407 869 9587, office: 408 884 9519 OR x31640}
| homepage: | http://purl.oclc.org/NET/edburns/
| aim: edburns0sunw | iim: ed.burns_at_sun.com