I don't think that there's any difference with writing the REST connectivity. That part would be the same whether you wrote a chat in Swing or in Tapestry, I think.
You would want to have a class somwhere with methods like listAllMessages, getCurrentMessage, et.c. which would communicate with the other RESTive classes. Then you tapestry page would use the getters and setters transparently in the Tapestry component you put on the page, for instance a textfield would look like; <span jwcid="@TextField" value="ognl:currentMessage"/> Which would fill itself when the page render by calling getCurrentMessage, and which would (when enclosed in a form (and maybe anyway :)) call setCurrentMessage on the class of the page when submitted. Cheers, PS On 5/20/06, Mário Lopes <[EMAIL PROTECTED]> wrote:
Hi! I want to build a web based chat. The client will connect with the server through REST requests. How can I build a service/component/servlet to manage this in Tapestry? Thanks. -- Mário --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
