Anyone interested in answering Jeoff's comment on my blog? ;-) I don't feel I know Tapestry well enough to answer his questions.
http://raibledesigns.com/page/rd?entry=tapestry_4_0_support_in#comments Thanks, Matt ---------- Forwarded message ---------- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Apr 5, 2006 2:31 PM Subject: Comment: Tapestry 4.0 support in AppFuse's CVS To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Jeoff Wilks wrote: Matt, I'm glad you spent the time learning Tapestry so that the rest of us don't have to. :) Seriously though-- my question is about how Tapestry uses session storage. Based on your experience, is it possible to develop a reasonably complex Tapestry web app without relying on session storage? The ultimate test: can the user safely bookmark any page on the site? (...and in the future, after logging in again, see all the same stuff on the screen). My impression from other reading is that Tapestry's automatic state management relies heavily on the HttpSession object to do its magic. As you are likely aware, session-based storage does not lend itself well to bookmarking. ________________________________ Respond to this comment at: http://raibledesigns.com/page/rd?entry=tapestry_4_0_support_in#comments ________________________________ Link to comment management page: http://raibledesigns.com/editor/commentManagement.do?method=query&entryid=ff8080810a145ed6010a523c0c5a3976 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
