ticketmaster type of site

[Andy G]

I need to create a site for registration of classes. The client wants the
system to 'hold' the class while the person is checking out so no one else
accessing the system can have access to the same class. I am in the
preliminary architechture stages of the system and am just trying to get the
best practices down. Does anyone have any experienc, url's, threads that
they can point me to?

Thanks.

[Peter Bromberg [C# MVP]]

Basically you just need to have a bit field "OnHold" for the class table's
particular row so when somebody starts a checkout operation you can update
this row and set the column to "true" (1). Then you can release it when they
cancel, or after a period of time with no final "Checkout" by that user.

The rest of your stored procedures, if designed around this, should make
whatever you need to do relatively easy. Regarding sample code, urls, etc.
can't help there.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

I need to create a site for registration of classes. The client wants the
system to 'hold' the class while the person is checking out so no one else
accessing the system can have access to the same class. I am in the
preliminary architechture stages of the system and am just trying to get the
best practices down. Does anyone have any experienc, url's, threads that
they can point me to?

Thanks.

[Andy G]

So if I understand you right, when someone begins to register for one seat
in that class the entire class is on hold and no one else can register for
that class? If that's true, the on hold bit field will not work. There are
many seats in each class and we can't lock the class down until all those
seats are taken.

I'm thinking about creating another table that will hold one record for each
seat in the class and will have bit fields like 'Taken' and 'On Hold'. That
way the specific seat would be on hold, not the entire class.

Andy

"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:C2**********************************@microsof t.com...

Basically you just need to have a bit field "OnHold" for the class table's
particular row so when somebody starts a checkout operation you can update
this row and set the column to "true" (1). Then you can release it when
they
cancel, or after a period of time with no final "Checkout" by that user.

The rest of your stored procedures, if designed around this, should make
whatever you need to do relatively easy. Regarding sample code, urls, etc.
can't help there.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

>I need to create a site for registration of classes. The client wants
the
system to 'hold' the class while the person is checking out so no one
else
accessing the system can have access to the same class. I am in the
preliminary architechture stages of the system and am just trying to get
the
best practices down. Does anyone have any experienc, url's, threads that
they can point me to?

Thanks.

[Peter Bromberg [C# MVP]]

No, I meant put a hold on the seat that they are expected to take.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

So if I understand you right, when someone begins to register for one seat
in that class the entire class is on hold and no one else can register for
that class? If that's true, the on hold bit field will not work. There are
many seats in each class and we can't lock the class down until all those
seats are taken.

I'm thinking about creating another table that will hold one record for each
seat in the class and will have bit fields like 'Taken' and 'On Hold'. That
way the specific seat would be on hold, not the entire class.

Andy

"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:C2**********************************@microsof t.com...

Basically you just need to have a bit field "OnHold" for the class table's
particular row so when somebody starts a checkout operation you can update
this row and set the column to "true" (1). Then you can release it when
they
cancel, or after a period of time with no final "Checkout" by that user.

The rest of your stored procedures, if designed around this, should make
whatever you need to do relatively easy. Regarding sample code, urls, etc.
can't help there.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

I need to create a site for registration of classes. The client wants
the
system to 'hold' the class while the person is checking out so no one
else
accessing the system can have access to the same class. I am in the
preliminary architechture stages of the system and am just trying to get
the
best practices down. Does anyone have any experienc, url's, threads that
they can point me to?

Thanks.

[Andy G]

Awesome, wasn't clear before. We're on the same page now.
"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:B8**********************************@microsof t.com...

No, I meant put a hold on the seat that they are expected to take.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

>So if I understand you right, when someone begins to register for one
seat
in that class the entire class is on hold and no one else can register
for
that class? If that's true, the on hold bit field will not work. There
are
many seats in each class and we can't lock the class down until all those
seats are taken.

I'm thinking about creating another table that will hold one record for
each
seat in the class and will have bit fields like 'Taken' and 'On Hold'.
That
way the specific seat would be on hold, not the entire class.

Andy

"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in
message
news:C2**********************************@microso ft.com...

Basically you just need to have a bit field "OnHold" for the class
table's
particular row so when somebody starts a checkout operation you can
update
this row and set the column to "true" (1). Then you can release it when
they
cancel, or after a period of time with no final "Checkout" by that
user.

The rest of your stored procedures, if designed around this, should
make
whatever you need to do relatively easy. Regarding sample code, urls,
etc.
can't help there.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Andy G" wrote:

I need to create a site for registration of classes. The client wants
the
system to 'hold' the class while the person is checking out so no one
else
accessing the system can have access to the same class. I am in the
preliminary architechture stages of the system and am just trying to
get
the
best practices down. Does anyone have any experienc, url's, threads
that
they can point me to?

Thanks.