|
URL re-writing, hidden form posts, agreed, all of these are hokey ways of
keeping a unique identifier for a user, but you can't rely 100% on
cookies... but, whats a developer to do? =)
Jeremy
At 03:44 PM 4/27/00 -0400, Steve Thurber wrote:
The better B2C internet commerce applications only use cookies as you
describe -- to identify the user/session so that the full session context
can be restored from a database. But the drawback is that the site won't
work for a user who has disabled cookie use in the browser. Other common
approaches are stashing data on the page or in the address -- both of
which are more exposed.
===
---- Jeremy Johnson <jjohnson@xxxxxxxx> wrote:
> At 12:04 PM 4/27/00 -0700, Wayne wrote:
> >Do you have document that you mentioned that we can reference?
> Sure. http://www.linux-vs.org/persistence.html
>
>
> >Most shopping cart we tried using cookie to keep the shopping information.
> >Do you have any suggestion that a shopping cart not using cookie
> at all?
> Well, a cookie is good for stashing some information, but I don't think
>
> cookies should be used for more than recognizing you when you return
> to a
> site.... everything else about a user should be stashed in a central
>
> storage area, IE database, NFS mount, etc....
>
> If you REALLY want to know what I would do, I would run roxen as the
>
> webserver (www.roxen.com). It has a really simplistic database interface,
>
> could make setting/getting/editing the database shopping cart quite
> easy...
>
>
> >Thanks Jeremy!
> No Problem ;)
>
> Jeremy
>
>
>
>
>
__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
|
