On 4/15/05, Michael J. <[EMAIL PROTECTED]> wrote:
> I prefer to store everything on the server. It gives better control
> over data and application state.
>
> > Brian
> >
> > I vote for storing information in session variables for
> > the simple reason most Admins do not allow Browsers
> > writing
I prefer to store everything on the server. It gives better control
over data and application state.
> Brian
>
> I vote for storing information in session variables for
> the simple reason most Admins do not allow Browsers
> writing cookies on the hard drive for fear of introducing
> viruses to
Authentication information (user is logged in) must be stored on the
server side (session or database). It should not be given to the client,
because the client could manipulate it (setting isLoggedIn to true).
If you store it in the database you should use a non guessable random
number as a ke
For storing user info, using sessions is the best way. Think about not
using sessions: you should someway propagate an "ID" of the user between
requests. Luckily, J2EE applications store a session ID as a cookie or (if
cookies are not enabled) propagates it in URLs.
But be cautious using session, d
Brian
I vote for storing information in session variables for the simple reason
most Admins do not allow Browsers writing cookies on the hard drive for fear
of introducing viruses to the system
+1 for session variables
Martin Gainty
From: "Brian McGovern" <[EMAIL PROTECTED]>
Reply-To: "Struts
Use the
>> [EMAIL PROTECTED] 2/9/2005 3:47:19 PM >>>
Hi,
I'm planning my approach to a data driven app that I have to write in
the near future. I've used struts before in more of a demo-type, proof
of concept scenarios, and am no where near and expert, but now need to
build a production level s
6 matches
Mail list logo
