B
Billy Horne
Hi - I need to write a basic order page for our web site. It is very
straight-forward, in that we don't need a whole "shopping cart" system.
Instead we just need a list of products displayed with a quantity field, and
when they submit the form it then collects payment info, then they submit
again and it charges their card. I plan to use a third party component to
handle the credit card charging so that should be pretty easy.
My main concern is how to best make a simple web form that the users can use
to submit their orders. I have studied web forms and it looks ideal except
for one MAJOR catch - the posted back data seems to timeout after x minutes.
For example assume page 1 of the order form asks for quantities of each
item. Then that is posted back and they get the customer information page
next. Now, if they sit on that page for say an hour before doing anything
when they continue and submit the form I think all the previously posted
data is lost because the session times out, right? I assume I can bump the
timeout, but what if they go home for the night and continue the next day or
a long scenario like that?
With this in mind, it seems like the traditional approach of just using
regular home grown forms and managing posted data manually (i.e. the type of
approach taken with classic ASP) has a great advantage in this regard. Am I
right, or am I missing something? How can you best account for the
possibility of long delays between each postback?
Also while we are on the subject; can anyone recommend a sample that
demonstrates how to make a basic ordering system like this. Like I
mentioned above I am not looking for anything complex or anything that
allows them to browse and add items to a cart and all that. Just need to
have them say I want x of these, and x of those and here is my credit card.
Bill
straight-forward, in that we don't need a whole "shopping cart" system.
Instead we just need a list of products displayed with a quantity field, and
when they submit the form it then collects payment info, then they submit
again and it charges their card. I plan to use a third party component to
handle the credit card charging so that should be pretty easy.
My main concern is how to best make a simple web form that the users can use
to submit their orders. I have studied web forms and it looks ideal except
for one MAJOR catch - the posted back data seems to timeout after x minutes.
For example assume page 1 of the order form asks for quantities of each
item. Then that is posted back and they get the customer information page
next. Now, if they sit on that page for say an hour before doing anything
when they continue and submit the form I think all the previously posted
data is lost because the session times out, right? I assume I can bump the
timeout, but what if they go home for the night and continue the next day or
a long scenario like that?
With this in mind, it seems like the traditional approach of just using
regular home grown forms and managing posted data manually (i.e. the type of
approach taken with classic ASP) has a great advantage in this regard. Am I
right, or am I missing something? How can you best account for the
possibility of long delays between each postback?
Also while we are on the subject; can anyone recommend a sample that
demonstrates how to make a basic ordering system like this. Like I
mentioned above I am not looking for anything complex or anything that
allows them to browse and add items to a cart and all that. Just need to
have them say I want x of these, and x of those and here is my credit card.
Bill