Patrick Casey wrote: > > The more I work with tapstry, the less comfortable I am trusting > the rewind process and/or the users not to push back. So I'm ending up > rolling a lot of my pre tapestry techniques in to make a "pseudo-stateless" > environment where basically the only thing I have stuffed in the visit > object is the User's login state.
Same experience here. We ended up using DirectLinks only. No ActionLinks, even for trivial actions. (If it's a trivial enough action that an ActionLink is reliable -- e.g., no parameters or objecs to be retrieved from the page -- then the DirectLink is equally simple.) Each DirectLink carries the id of the object if one is needed and we refetch the object when the link is clicked. (The object is in the cache anyway, using Cayenne's DataObjectUtils.) We don't do anything on rewind and our app fears no button. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
