French, Shawn wrote:
> Stas Bekman wrote:
>
>>It seems that you are after the same functionality as Apache::DBI, you
>>want a pool of items that you want to be able to choose from.
>>Look for threads::shared (perl 5.8.0), just create a shared hash with
>>keys that you use for the map and the v
Stas Bekman wrote:
> It seems that you are after the same functionality as Apache::DBI, you
> want a pool of items that you want to be able to choose from.
> Look for threads::shared (perl 5.8.0), just create a shared hash with
> keys that you use for the map and the values for the actual conn
French, Shawn wrote:
> Hey everyone,
>
> It's me again... the persistent telnet mod_perl newbie!
> (http://msgs.securepoint.com/cgi-bin/get/apache0205/204.html)
>
> I have implemented my project using persistent telnet connections (one for
> each user session accessible throught the session to p
French, Shawn wrote:
> Recall that I am using: Apache/1.3.20 (Win32) mod_perl/1.25_01-dev
> mod_ssl/2.8.4 OpenSSL/0.9.6a on Windows 2000 with PHP 4.21
>
> Would this be why my scripts are working?
Mystery solved! Yes, that's why. You are running mod_perl in single
process mode because you're
"French, Shawn" wrote:
>
> I just found this: http://www.devshed.com/Talk/Books/ProApache/page2.html
>
> "On Windows platforms, Apache does not fork; consequently, the directives
> for controlling the number of processes or their lifetime have no effect.
> Instead, Apache runs as a multi-threade
ns'
> Cc: [EMAIL PROTECTED]
> Subject: RE: Persistent Net::Telnet Objects
>
>
> Perrin wrote:
> > I can't see how it could be working now
>
> That makes two of us!
>
> > You're probably opening new telnet connections from each apache
> >
I just found this: http://www.devshed.com/Talk/Books/ProApache/page2.html
"On Windows platforms, Apache does not fork; consequently, the directives
for controlling the number of processes or their lifetime have no effect.
Instead, Apache runs as a multi-threaded process"
Recall that I am using:
Perhaps you can put a System V message Queue in front of both Telnet
connections, this way producers can place their messages in the queue
asynchronously , and the backend (consumer) can pick them up in a FIFO.
Also, try using Net::SSH::Perl. The Net::Telnet does not give your things
like
STDOUT,
Our project needed persistent socket connections open as well. There is
supposed to be a standard mechanism to pass file descriptors between unix
processes, though it's bugginess level depends on your OS. There is a perl
module for this called Socket::PassAccessRights. So what you can do is
create
Maybe you can tell us more about the project (e.g. why
telnet ?) so there will come many bad advices ? :-)
Peter Bi
> Perrin wrote:
> > I can't see how it could be working now
>
> That makes two of us!
>
> > You're probably opening new telnet connections from each apache process.
>
> I know
Perrin wrote:
> I can't see how it could be working now
That makes two of us!
> You're probably opening new telnet connections from each apache process.
I know that I am not since they are continuing to log to the same dump file,
and my code (as stated in previous message) simply goes to the ha
French, Shawn wrote:
> Although this is working right now, I don't know enough [ anything? :) ]
> about Apache or mod_perl to be sure that this will work in the future.
I can't see how it could be working now, unless it is actually creating
a new Telnet object on every request. Your %sessionHas
12 matches
Mail list logo
