Correctly Programming in Perl CGI / Accessing the same data from differ perl cgi files?

To re-iterate what Sinan said, the shopping cart needs to be done using sessions I will try to explain a bit more about how it all works, since your question seems to imply you would like to understand the details There are two concepts that are involved: A Session Cookie, and a Session database on the server side Your web server has an internal "sessions" database - which is basically a mapping between a long string known as the "Session Key" and a blob of data. This database can be built into the web server, or in case of Perl CGI, be implemented by a special Perl module What gets stored in this blob of data in a Session database? Anything your CGI script decides to store - in your case, the current state of the shopping cart How does the information get shared between the pages?

A special Session Cookie is generated by your session module, with the value of the cookie being the same "Session Key" used to store the blob of data on the server in session database. It is then stored by the user's browser like all the other cookies, except its value is only valid "for the duration of a session" - it expires after a short period of time or if you close your browser. Then, when the user continues with the web app, the cookie value gets sent back to the server and therefore your CGI script knows to re-use that session key NOTE : An alternate approach (instead of using a cookie) is to pass the session ID value between all your requests (e.g. Code it into all GET URLs and POST forms) As far as Perl CGI implementation, it depends on the specific Perl web framework you use - the basic session work can be done using CGI::Session CPAN module (there is a good tutorial for it as well ).

Another frequent option for those using Apache web server is Apache::Session What a general Session related module does is provide you with the APIs to: Manage Session database Store/retrieve data in Session database using Session key (aka Session ID) Obtain the user's current session ID (from the session cookie value), if any Generate a new session ID for the user, if needed Send the session ID value as a cookie to be stored in HTTP response to user's browser Any decent Perl web framework has session capabilities built in (they are still implemented using some sort of Session management Perl module, but the framework provides easy-to-use APIs As an example of "easy to use", in Embperl, to store a value in a session, all you do is $udat{shopping_cart} = \%shopping_cart_data and to retrieve it you do %shopping_cart_data = %$udat{shopping_cart} %udat being a special hash name). That's it. All the details hidden from you by the framework UPDATE: This has pretty much nothing to do with what seems to me the actual question being asked, but it's nevertheless a valid point that a comment to this answer made me think of In the interest of improving the overall quality of your code, you should always abstract away as much of the general business logic.

In this case, if you have any generic logic for working with the shopping cart data which is shared between your different Perl CGI scripts, that logic should be abstracted away into a separate Perl module In addition, as further improvements: You should consider MVC (model-view-controller) design for any complicated web app. To make this easier, pick an MVC-compliant Perl web framework (I think Catalyst is considered the main option these days but do your own research before setting on one You should also have a design that allows you to modularize and re-use web (view) elements - e.g. The top var of the application that probably will display # of items in the shopping cart would always be pretty much the same HTML, and you should not duplicate that HTML across different views. (if you aren't sure what I'm talking about, look at top 2 lines on Amazon's web page).

There are different techniques for achieving that, which go well beyond the scope of your question (frames, web frameworks with merged views, Perl module for View printing, etc...).

To re-iterate what Sinan said, the shopping cart needs to be done using sessions. I will try to explain a bit more about how it all works, since your question seems to imply you would like to understand the details. There are two concepts that are involved: A Session Cookie, and a Session database on the server side.

Your web server has an internal "sessions" database - which is basically a mapping between a long string known as the "Session Key" and a blob of data. This database can be built into the web server, or in case of Perl CGI, be implemented by a special Perl module. What gets stored in this blob of data in a Session database?

Anything your CGI script decides to store - in your case, the current state of the shopping cart. How does the information get shared between the pages? A special "Session Cookie" is generated by your session module, with the value of the cookie being the same "Session Key" used to store the blob of data on the server in session database.It is then stored by the user's browser like all the other cookies, except its value is only valid "for the duration of a session" - it expires after a short period of time or if you close your browser.

Then, when the user continues with the web app, the cookie value gets sent back to the server and therefore your CGI script knows to re-use that session key. NOTE: An alternate approach (instead of using a cookie) is to pass the session ID value between all your requests (e.g. Code it into all GET URLs and POST forms). As far as Perl CGI implementation, it depends on the specific Perl web framework you use - the basic session work can be done using CGI::Session CPAN module (there is a good tutorial for it as well).

Another frequent option for those using Apache web server is Apache::Session. What a general Session related module does is provide you with the APIs to: Manage Session database Store/retrieve data in Session database using Session key (aka Session ID) Obtain the user's current session ID (from the session cookie value), if any Generate a new session ID for the user, if needed Send the session ID value as a cookie to be stored in HTTP response to user's browser. Any decent Perl web framework has session capabilities built in (they are still implemented using some sort of Session management Perl module, but the framework provides easy-to-use APIs.

As an example of "easy to use", in Embperl, to store a value in a session, all you do is $udat{shopping_cart} = \%shopping_cart_data and to retrieve it you do %shopping_cart_data = %$udat{shopping_cart} - %udat being a special hash name). That's it. All the details hidden from you by the framework.

UPDATE: This has pretty much nothing to do with what seems to me the actual question being asked, but it's nevertheless a valid point that a comment to this answer made me think of.In the interest of improving the overall quality of your code, you should always abstract away as much of the general business logic. In this case, if you have any generic logic for working with the shopping cart data which is shared between your different Perl CGI scripts, that logic should be abstracted away into a separate Perl module. In addition, as further improvements: You should consider MVC (model-view-controller) design for any complicated web URL3 make this easier, pick an MVC-compliant Perl web framework (I think Catalyst is considered the main option these days but do your own research before setting on one.

You should also have a design that allows you to modularize and re-use web (view) elements - e.g. The top var of the application that probably will display # of items in the shopping cart would always be pretty much the same HTML, and you should not duplicate that HTML across different views.(if you aren't sure what I'm talking about, look at top 2 lines on Amazon's web page). There are different techniques for achieving that, which go well beyond the scope of your question (frames, web frameworks with merged views, Perl module for View printing, etc...).

Sessions are important, but they answer the question only partly, they don't tell you how to structure your code into individual Perl files. – reinierpost Feb 11 at 9:39 1 @reinierpost - I'm not sure what you mean - please clarify. Her main question was how to share her shopping cart between different page views."Structuring" code between individual Perl files has nothing to do with that and depend 100% on both her logic, details of her pages, whether she uses MVC approach and which web framework she uses .

– DVK Feb 11 at 12:49 Good answer, I want to add that a cookie isn't strictly necessary if you use session ids in all URLs (including form posts etc). Obviously they still must be tied to and managed/authenticated from the back end.(Note, I am sure you already knew this, I just wanted it in the thread.) This session style was more common a decade ago when cookies were still mildly controversial; and sites like Amazon. Com still support it.

– Ashley Feb 11 at 15:39 1 @Ashley - good point. I didn't realize people still use cookie-less sessions these days, but it definitely is a perfectly valid approach. Edited.

– DVK Feb 11 at 16:31.

The short answer is: You are doing it all wrong. You need to store the contents of the shopping cart for each visitor on the server side using server side sessions. See, for example, My Experiences with using CGI::Application and Template::Toolkit To Build an Online Shopping Cart by Justin Simoni.

If you try to store the contents of the shopping cart in HTML pages you serve, malicious visitors can easily change, say, prices and give themselves nice discounts as people discovered in the mid nineties.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.