comment on

Remember that the World Wide Web is intrinsically stateless (See What is stateless?), and this means that "trying to persist an application across web requests" is going against the grain from the outset.

It might be conceptually easier to think of your "persistent" application in client-server terms, where you interact with your application (server) using a web browser (client) to communicate messages. For example, your server application could respond to client "messages" that are queued in a file, taking action when it encounters new messages.

On the other hand, if you really want to persist with persistence <grin> then there are various options such as cookies (client side persistence) or CGI::persistent (server side persistence).

Good luck, and let us know what you decide.

In reply to Re: Persist shell app by EdwardG
in thread Persist shell app by geoffeg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks