Hi Monks, I am facing a data persitence problem. In my application, on a web page I am taking a file(report file) name from the user and then printing that file on the browser itself. Similarly i have to print few specified lines from the same report file and print them on the browser. For that i don't want to take the any input from the user but while making another request to the web server the inputs initially taken are lost. So, i am writing them to a file and using them again later on. Now the problem is when i am running multiple instances of the same application, the file is overwritten and i am not able to associate the data with each request. kindly help me, so either i could save the data of the initial request made or could associate data with each server request. Thanks in advance.!!!

In reply to data persistence by need_help21

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.