Yes, exactly. XMLHttpRequest will be sending other types of events than ":action", such as ":refresh", ":update" ... whatever makes sense.
The event handler methods will respond with new response types that will be capable of sending back text, html and json responses to accomplish various things on the client side. The design of events and mixins in T5 were guided by needs of these use-cases. On 3/10/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
Howard would you mind sharing some more thoughts on this sentence found on the request processing doc: "In cases where the event type is not the default, "action", it will appear between the nested component id and the event context, preceded by a colon. Example: "/example/foo.bar:magic/99" would trigger an event of type "magic". This is not common in the vanilla Tapestry framework, but will likely be more common as Ajax features (which would not use the normal request logic) are implemented." What's the actual meaning of "which would not use the normal request logic"? Do you plan to extend the current dispatcher facility or you were simply talking about the usage of XMLHttpRequest instead of 'normal browser requests'? Regards -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
