[Persistentperl-users] Followup to my STDOUT issue
Brought to you by:
samh
From: Dallas E. <da...@nm...> - 2003-03-13 17:58:19
|
I was reading the docs on how speedy works, and seen When executed, the speedy frontend does the following: 1. Looks for an available backend to run this script. 2. If no backends are available, starts a new one. 3. As soon as a backend is located, connects to it and starts to send = over %ENV, @ARGV and the STDIN data. 4. Brings back the STDOUT and STDERR data from the backend and sends = it to its output.=20 The speedy backend does the following: 1. Initializes the perl interpreter and compiles the perl script 2. Waits for a frontend to contact it 3. Once a frontend contacts it, reads in and initializes %ENV and = @ARGV 4. Sets up STDIN, STDOUT and STDERR so that they are connected to the = frontend via Unix sockets. 5. Executes the perl code. 6. Goes back and waits for another frontend to contact it.=20 When I look at Step 3 on how speedy works, I see that it does not pipe = STDOUT to the backend? How am I supposed to read STDOUT from a previous = pipe into my script?? Like the one I posted before. I'm trying to = write a filter that mail pipes through, but I dont want to invoke a perl = interpreter for each email! In order to get the envelope addresses, I = have to read STDOUT from the qmail-smtpd pipe to my script. Is this impossible with perperl or should I maybe look into fastcgi? Thanks. Dallas |