>To identify the user and create a relationship TO the data on the server.
I use the session.sessionid.  Of course I also use ASP, so this might not
be available to everyone.

>Both are required - the 'cart' is kept on the server, .. the cookie is
used to identify WHICH cart belongs to THAT user.
I see.  I guess this is true, most of the time.  I dont use any cookies
ever, but use the session id to track the user to cart connection.  It does
have its downsides, like for peole that come from the same proxy, etc.


>
>They must either accept  the cookie, .. or the designers can choose to not
use them (we prefer to use a 'Car ID' passed as a hidden field from one
form to the next, .. avoiding the cookie issue entirely).
Yes I suppose that is about the same thing I do.  I pass the sessionid from
one application to the secure site for checkout, etc etc.

thanks!


Phil Babcock
Lead Web Designer
BGS Group Inc.

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA