It depends on the scope you really need. Application is like a safer
variant of static and thus is shared by all clients. If you work with
state on that level, consider thread safety. Session makes sense if
you have state that you want to have available throughout *your whole*
session, like the log
and yes the application object is a singleton.-IgorOn 2/9/06, Johan Compagner <[EMAIL PROTECTED]
> wrote:you shouldn't use the Http session directlyBut using the Wicket session object (or a wikcet session sub clas object of youre own) can be used fine to share global information (like the logged in
you shouldn't use the Http session directlyBut using the Wicket session object (or a wikcet session sub clas object of youre own) can be used fine to share global information (like the logged in user)sharing information between pages for page construction i would do through special page constructor
Others have asked about sharing
information between pages, and the answer has been to pass the shared
information via page constructors.
Since no one suggested using the WebApplication
object, does that imply that this is a singleton shared by all clients?
It has been said that it is p
