Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

jpcardoso,

I'm glad I could help you, but I also have to agree with the other monks about waiting 5 minutes for a response. That's a really long time on the web today. Most users expect responses in seconds, not minutes. Doing this lookup with 'ajax' would be nice, but it would also be a lot of work.

Maybe, let us help you with the real problem -- having to 'grep' on a 'bz2' file. Perl is very good at reading a file and searching ( 'index' ). Several generic fixes come to mind, but some more information about the data(bz2 file) would help us give you some better options.

But just in case you can't get around the 'grep', you could schedule it and immediately return a HTML page informing the user that it will take 'x' minutes to get a response and to check back in a few minutes. Provide a link to check on the status. Once the response is available, return the current page that you are returning now.

You may also want to look at the problem of denial of service (DOS) with longer time-outs. The apache web site describes this in detail. Better to plan now, than get the web site finished and then have a DOS attack.

Best of Luck...Ed

"Well done is better than well said." - Benjamin Franklin


In reply to Re^3: request timing out on Perl Web by flexvault
in thread request timing out on Perl Web by jpcardoso

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



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (7)
As of 2024-03-28 19:47 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found