VbzCart/pieces/sessions - Revision history

Woozle: Woozle moved page VbzCart/session to VbzCart/pieces/sessions without leaving a redirect: reorg

2016-06-04T16:08:53Z

Woozle moved page VbzCart/session to VbzCart/pieces/sessions without leaving a redirect: reorg

← Older revision	Revision as of 16:08, 4 June 2016
(No difference)

Woozle: post-import note about being dated

2012-12-21T03:27:14Z

post-import note about being dated

← Older revision		Revision as of 03:27, 21 December 2012
Line 1:		Line 1:
	~~[[Technology]]: [[VbzCart]]: [[VbzCart Session\|Session]]~~		==Note==
			This documentation was last edited in 2008, and should be checked for accuracy.
	A ~~[[VbzCart Session\|~~session]] is when a particular user is connected to VbzCart using a particular browser on a particular computer.		==About==
			A '''session''' is when a particular user is connected to [[VbzCart]] using a particular browser on a particular computer.

	Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).		Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).

Woozle: Woozle moved page VbzCart Session to VbzCart/session without leaving a redirect

2012-12-21T03:25:00Z

Woozle moved page VbzCart Session to VbzCart/session without leaving a redirect

← Older revision	Revision as of 03:25, 21 December 2012
(No difference)

Woozle: 5 revisions

2012-12-21T03:24:27Z

5 revisions

← Older revision	Revision as of 03:24, 21 December 2012
(No difference)

Woozle: VbzCart Session ENJOYING BRIAN PEPPERS DAY??? moved to VbzCart Session over redirect: reverting "Brian Peppers Day" vandalism

2008-08-05T23:18:07Z

VbzCart Session ENJOYING BRIAN PEPPERS DAY??? moved to VbzCart Session over redirect: reverting "Brian Peppers Day" vandalism

New page

[[Technology]]: [[VbzCart]]: [[VbzCart Session|Session]]

A [[VbzCart Session|session]] is when a particular user is connected to VbzCart using a particular browser on a particular computer.

Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).

A session also helps keep track of user preferences, e.g. searching only certain item types or topics.

==Identifying a Session==
I've been debating about the idea of allowing carts to work using IP address/domain plus browser ID (user_agent) because cookies don't always seem to work (and some people have them turned off), and I think I've come up with a reasonable compromise.

The problem is that one user might connect through a dial-up (dynamic IP), place orders in a cart and disconnect, and then another user with the same browser and OS might happen to connect through the same dial-up -- which would cause that user to be assigned the previous user's shopping cart. This isn't a ''serious'' problem, because no personal information will be conveyed, but it can be off-putting to go to a store and find that your cart already has items in it. I would be inclined to immediately go somewhere else if I encountered this.

What I've come up with is the following:
*sessions IDed via IP/browser have a much shorter expiration than cookie sessions
*sessions IDed via IP/browser will show a warning to indicate the shorter expiration time (should show the time when the session will expire -- and the current time, to prevent timezone confusion)
*cookies have never been used for checkout; we have always used POST data (?session=xxxxx), so that's not an issue

==Sequence of Events==
*On receiving one or more items to add to the cart:
*#Try to match with existing session:
*#*Check for session cookie; if found, use that
*#*If no session cookie, look for unexpired IP/browser match
*#If no usable existing session found, create a new one (empty cart)
*#Add items to the session cart
*#Display cart & session info

Woozle: added note about sessions tracking user prefs

2005-07-26T12:05:53Z

added note about sessions tracking user prefs

← Older revision		Revision as of 12:05, 26 July 2005
Line 1:		Line 1:
	[[Technology]]: [[VbzCart]]: [[VbzCart Session\|Session]]		[[Technology]]: [[VbzCart]]: [[VbzCart Session\|Session]]

	A [[VbzCart Session\|session]] is when a particular user is connected to VbzCart using a particular browser on a particular computer. Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).		A [[VbzCart Session\|session]] is when a particular user is connected to VbzCart using a particular browser on a particular computer.

			Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).

			A session also helps keep track of user preferences, e.g. searching only certain item types or topics.

	==Identifying a Session==		==Identifying a Session==

Woozle at 22:02, 25 July 2005

2005-07-25T22:02:06Z

← Older revision		Revision as of 22:02, 25 July 2005
Line 1:		Line 1:
	[[Technology]]: [[VbzCart]]: [[VbzCart ~~Sessions~~\|~~Sessions~~]]		[[Technology]]: [[VbzCart]]: [[VbzCart Session\|Session]]

	==Identifying ~~Sessions~~==		A [[VbzCart Session\|session]] is when a particular user is connected to VbzCart using a particular browser on a particular computer. Multiple carts may be created in a single session, as well as multiple orders. The same cart may not be accessed from different sessions; the user needs to save the cart to something which can be identified humanly, i.e. an order (or, in the future, perhaps a wish list).

			==Identifying a Session==
	I've been debating about the idea of allowing carts to work using IP address/domain plus browser ID (user_agent) because cookies don't always seem to work (and some people have them turned off), and I think I've come up with a reasonable compromise.		I've been debating about the idea of allowing carts to work using IP address/domain plus browser ID (user_agent) because cookies don't always seem to work (and some people have them turned off), and I think I've come up with a reasonable compromise.

	The problem is that one user might connect through a dial-up (dynamic IP), place orders in a cart and disconnect, and then another user with the same browser and OS might happen to connect through the same dial-up -- which would cause that user to be assigned the previous user's shopping cart. This isn't a ''serious'' problem, because no personal information will be conveyed, but it can be off-putting to go to a store and find that your cart already has items in it. I would be inclined to immediately go somewhere else.		The problem is that one user might connect through a dial-up (dynamic IP), place orders in a cart and disconnect, and then another user with the same browser and OS might happen to connect through the same dial-up -- which would cause that user to be assigned the previous user's shopping cart. This isn't a ''serious'' problem, because no personal information will be conveyed, but it can be off-putting to go to a store and find that your cart already has items in it. I would be inclined to immediately go somewhere else if I encountered this.

	What I've come up with is the following:		What I've come up with is the following:
Line 13:		Line 15:
	==Sequence of Events==		==Sequence of Events==
	*On receiving one or more items to add to the cart:		*On receiving one or more items to add to the cart:
	**Try to match with existing session:		*#Try to match with existing session:
	***Check for session cookie; if found, use that		#Check for session cookie; if found, use that
	***If no session cookie, look for unexpired IP/browser match		#If no session cookie, look for unexpired IP/browser match
	**If no usable existing session found, create a new one (empty cart)		*#If no usable existing session found, create a new one (empty cart)
	**Add items to the session cart		*#Add items to the session cart
	**Display cart & session info		*#Display cart & session info

Woozle at 18:10, 25 July 2005

2005-07-25T18:10:38Z

New page

[[Technology]]: [[VbzCart]]: [[VbzCart Sessions|Sessions]]

==Identifying Sessions==
I've been debating about the idea of allowing carts to work using IP address/domain plus browser ID (user_agent) because cookies don't always seem to work (and some people have them turned off), and I think I've come up with a reasonable compromise.

The problem is that one user might connect through a dial-up (dynamic IP), place orders in a cart and disconnect, and then another user with the same browser and OS might happen to connect through the same dial-up -- which would cause that user to be assigned the previous user's shopping cart. This isn't a ''serious'' problem, because no personal information will be conveyed, but it can be off-putting to go to a store and find that your cart already has items in it. I would be inclined to immediately go somewhere else.

What I've come up with is the following:
*sessions IDed via IP/browser have a much shorter expiration than cookie sessions
*sessions IDed via IP/browser will show a warning to indicate the shorter expiration time (should show the time when the session will expire -- and the current time, to prevent timezone confusion)
*cookies have never been used for checkout; we have always used POST data (?session=xxxxx), so that's not an issue

==Sequence of Events==
*On receiving one or more items to add to the cart:
**Try to match with existing session:
***Check for session cookie; if found, use that
***If no session cookie, look for unexpired IP/browser match
**If no usable existing session found, create a new one (empty cart)
**Add items to the session cart
**Display cart & session info