As most of my work with Tapestry has been focused on building a stateless site, please forgive my ignorance if apparent.
Having now got my new Tapestry 4 site working beautifully, and with a dramatic performance improvement of 2 to 3 times, I am starting to plan revamping my currently primitive admin site. I was revisiting ASO and persistent properties, and then I asked myself a simple question. If I use hivemind services to keep and retrieve persistent user specific information, so that I can do mock/unit testing easily, and I use persistent page/component properties for that which is tied directly to the session; When would I ever use ASO, besides identifying the authenticated user ? Before you answer, when you need the same persistent information across multiple pages, please give me a concrete example. In the sort of applications I make most information is tied to the user and needs to be persisted to a database/directory, so it is available beyond the current session. So when would you use an ASO ? Henrik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
