[OT] - Login Application

[Jonathan Hawkins <jh...@chestnet.org>]

Howdy All,
I am writing a custom login application.
Our organization has several web applications (Struts of course!)
one of which is a shopping cart.


The current login application adds two cookies to the users browser - 
one that stores a number representing a price index and the other an id.
(Meaning different users pay different amounts for products depending 
on their level of membership).

The issue:
I am adding a 30 day persistence feature to the login if the user 
selects a check box at login time.
It is possible that a users price index will change within a 30 day 
period due to advancement in their membership.

Should the shopping cart (or any other app that needs to calculate 
price) be responsible for getting the price index vs. the login getting 
it?

Has anyone had a similar situation and if so, how did you solve it?


Thanks in advance,
Jonathan Hawkins
Web Programmer
American College of Chest Physicians


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org

Re: [OT] - Login Application

[Martin Gainty <mg...@hotmail.com>]

Jonathan-
The peristence or even existence of any data entity can be ascertained from
the DB schema
what constraints have you placed on the creation of the Price Index?
what relationship does the Price Index have to the username/password ?
If the Price Index is constrained (or dependent on ) the existence of a
username/password then yes tie the PriceIndex into the Login
If the Price Index is not dependent on username/password then the PriceIndex
information cookies et al) should exist indepedently..
~my 2 cents~
-Martin
----- Original Message ----- 
From: "Jonathan Hawkins" <jh...@chestnet.org>
To: "Struts List" <st...@jakarta.apache.org>
Sent: Tuesday, December 09, 2003 2:18 PM
Subject: [OT] - Login Application


> Howdy All,
> I am writing a custom login application.
> Our organization has several web applications (Struts of course!)
> one of which is a shopping cart.
>
>
> The current login application adds two cookies to the users browser -
> one that stores a number representing a price index and the other an id.
> (Meaning different users pay different amounts for products depending
> on their level of membership).
>
> The issue:
> I am adding a 30 day persistence feature to the login if the user
> selects a check box at login time.
> It is possible that a users price index will change within a 30 day
> period due to advancement in their membership.
>
> Should the shopping cart (or any other app that needs to calculate
> price) be responsible for getting the price index vs. the login getting
> it?
>
> Has anyone had a similar situation and if so, how did you solve it?
>
>
> Thanks in advance,
> Jonathan Hawkins
> Web Programmer
> American College of Chest Physicians
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org