in reply to Re: Storing an array in a cookie...
in thread Storing an array in a cookie...

I dissagree. IMHO cookies should only really be used for session id's simply becuase of the random volatile nature of them.

I especially disagree in this case becuase if the data in the cookie is used for cash reimbursement is it particularly poor design IMO. In my experience with end users, sales reps on the road etc are not particularly technical, and can do amazing things to their machines (deleting directories etc), hence losing their data and the cash they would have got from it.

Having a persistant data store need not be difficult. It can be as easy as a flat file with DBI (or not) or be as complex as a many table, lots of data, normalised RDBMS information system.

I'm on the wagon of using the cookie for a sess_id then cross referencing it to a user and associated data.

++ for being brave enuff to kick the wagon and offer an alternative backed up by argument.

  • Comment on Re: Re: Storing an array in a cookie...

Replies are listed 'Best First'.
Re: Storing an array in a cookie...
by Nacho37 (Initiate) on Mar 04, 2002 at 22:16 UTC
    This application is meant as a "Sit and do it all at one time" application. I don't care about the cookie after the user enters his data 20 or 30 times and prints the final formatted page. The page is submitted to a higher beaurocracy than I for verification anyways. I am just looking to save several hundred people an hour's time each month in authoring mileage reimbursements. I want to get away from flipping thru several pages of "official mileage reimbursement distances" and just have people enter data one trip at a time and have the math done for them. I want it dated for each trip, in such a way that they specify what day of the month they made the trip. Thanks all for the insight into cookies, size limits, etc.

    Maybe someday I will incorporate authentication, stored databases of user mileage, higher security and the rest, but for now all I need to do is get the data to flow properly from query to query.