I think this is a workflow issue, and falls into the domain of Spring Web Flow. SWF folks are working on a proper integration of Tapestry and SWF.
On 8/26/05, Michael Prescott <[EMAIL PROTECTED]> wrote: > I have an application where certain screens can only be shown based on a > user's state (in an underlying model). State changes with every page > request (merely viewing the page can mean you're in a new state). > > Because users can double-click or click multiple links rapidly > (effectively making concurrent, incompatible requests), I need to > implement 'validity' checks correctly, redirecting requests for pages > that shouldn't be shown. > > I can check the model's state in validate(), but that isn't sufficient > because a concurrent request to a different page might change the model > state immediately after the validate() call but before. I'm new enough > to Tapestry that I'm not sure how I can synchronize access to my model > at a scope that spans all of these callbacks. > > What's the typical way of handling this sort of thing? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta 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]
