RE: RE : start http request and move on

2004-11-05 Thread Christopher Maujean
On Fri, 2004-11-05 at 13:39, Larsen, Errin M HMMA/IT wrote: > > -Original Message- > > From: JupiterHost.Net [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 05, 2004 3:08 PM > > To: [EMAIL PROTECTED] > > Cc: Jose Nyimi > > Subject: Re:

Re: RE : start http request and move on

2004-11-05 Thread JupiterHost.Net
Hi, Hello :) I've been lurking on this thread for a bit, and now that you've jumped to children and fork and related topics I'll chime in! I found a lot of useful information about this sort of thing in "perldoc perlipc". Check out the stuff about Daemons and the REAPER subroutine in that doc.

RE: RE : start http request and move on

2004-11-05 Thread Larsen, Errin M HMMA/IT
> -Original Message- > From: JupiterHost.Net [mailto:[EMAIL PROTECTED] > Sent: Friday, November 05, 2004 3:08 PM > To: [EMAIL PROTECTED] > Cc: Jose Nyimi > Subject: Re: RE : start http request and move on > > > > > Nice approach, I have learned toda

Re: RE : start http request and move on

2004-11-05 Thread JupiterHost.Net
Nice approach, I have learned today an easy to do it :) Though care should be taken to not fork many *uncontrolled* childs. Could you elaborate what uncontrolled children are specifically and what should be avoided? (In context of this thread of course not the little humans running around like c

RE : start http request and move on

2004-11-05 Thread Jose Nyimi
> -Message d'origine- > De : Bob Showalter [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 5 novembre 2004 19:40 > À : 'JupiterHost.Net'; [EMAIL PROTECTED] > Objet : RE: start http request and move on > > JupiterHost.Net wrote: > > Bob Showalter

Re: start http request and move on

2004-11-05 Thread JupiterHost.Net
You don't need to call exit if you just put the other stuff in an else {} block so the parent doesn't execute it. If you're running under Apache::Registry though, calling exit is OK. Perfect, the else {} works great! I'll need to read up on fork and all that so I can really get it :) Thanks so m

Re: start http request and move on

2004-11-05 Thread Gunnar Hjalmarsson
Bob Showalter wrote: If you're running under Apache::Registry though, calling exit is OK. If I have understood it correctly, it's not OK if Perl is older than 5.6. Therefore I'm using this sub: sub myexit { if ($ENV{MOD_PERL}) { if ($] < 5.006) { require A

RE: start http request and move on

2004-11-05 Thread Bob Showalter
JupiterHost.Net wrote: > Bob Showalter wrote: ... > > Use something like the following: ... > Thanks Bob, That works great! Now the next step is to play with that > in a peristent environment without killing the persistent process > with the exit() Perhapst the system + & will do better in a persi

Re: start http request and move on

2004-11-05 Thread JupiterHost.Net
Bob Showalter wrote: JupiterHost.Net wrote: I don't want the user to wait at all, just submit the form, they see the confirmation and close their browser and the fork() finished in its own sweet time on the server. Use something like the following: #!/usr/bin/perl use strict; use CGI ':sta

Re: start http request and move on

2004-11-05 Thread JupiterHost.Net
A very shoddy way of doing it, but you could put what you want to do in another script, call system() and place it in the background so you original script doesn't wait for it to return. . system "perl script.pl any arguments &"; . I assume this would work, but am not 100% sure without try

RE: start http request and move on

2004-11-05 Thread Murphy, Ged (Bolton)
-Original Message- From: JupiterHost.Net [mailto:[EMAIL PROTECTED] Sent: 05 November 2004 15:14 To: [EMAIL PROTECTED] Subject: Re: start http request and move on Thanks Jose, and Randal too :), very close indeed the only difference is I don't want the user to wait at all, just s

RE: start http request and move on

2004-11-05 Thread Bob Showalter
JupiterHost.Net wrote: > I don't want the user to wait > at all, just submit the form, they see the confirmation and close > their browser and the fork() finished in its own sweet time on the > server. Use something like the following: #!/usr/bin/perl use strict; use CGI ':standard'; us

Re: start http request and move on

2004-11-05 Thread JupiterHost.Net
Randal has written an excellent column and shown how to deal with such needs. Have a look to http://www.stonehenge.com/merlyn/LinuxMag/col39.html Thanks Jose, and Randal too :), very close indeed the only difference is I don't want the user to wait at all, just submit the form, they see the confi

RE: start http request and move on

2004-11-05 Thread NYIMI Jose \(BMB\)
> -Original Message- > From: JupiterHost.Net [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 03, 2004 10:23 PM > To: [EMAIL PROTECTED] > Subject: start http request and move on > > > Hey group, > > Not sure how I'd go about doing a url (via LWP probably) but > not wait for it t

Re: start http request and move on

2004-11-04 Thread JupiterHost.Net
say, it takes the entire http session 60 seconds from start to finish to submit the url, the script to run and return the results I want: print "Starting...\n"; nowaiturl("$url?foo=bar"); print "$url has been submitted, in appx 60 seconds it will finish"; to run in like it had been (obviously

Re: start http request and move on

2004-11-03 Thread JupiterHost.Net
The idea is to be able to submit data to $url for it to be processed (which may take a while) without waiting for it to finish. LWP::Parallel does mutiple $urls in parallel but I want to submit a single url like you would with LWP but not wait, does that make sense? Would a fork() of some sort

RE: start http request and move on

2004-11-03 Thread Moon, John
-Original Message- From: JupiterHost.Net [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 4:23 PM To: [EMAIL PROTECTED] Subject: start http request and move on Hey group, Not sure how I'd go about doing a url (via LWP probably) but not wait for it to return. print "Starti