RE: named pipes or files on disk?

"Brian Raven" <[email protected]>
Newsgroups gmane.comp.lang.perl.active-perl
Message-ID <[email protected]>
From: [email protected]
[mailto:[email protected]] On Behalf Of Jer A
Sent: 19 April 2010 23:54
To: [email protected]
Subject: named pipes or files on disk?

> All,
> 
> I am new to the concept of named pipes on unix/linux
> 
> by using 
> use Fcntl;
> will the named pipe transaction be faster than reading a file off the
hd?
> I am thinking a writing a daemon cron process, which a cgi process can
attach to
> and read from memory, instead of file.
> I dont want to use mod_perl.

This smells a bit like an XY problem (see
<http://www.perlmonks.org/index.pl?node_id=542341>), and I can't
immediately see what Fcntl has to do with pipes, named or otherwise. It
might help if we had more information about what you are trying to
accomplish. In any event, you might want to consider other IPC
mechanisms before pipes, like shared memory or sockets.

Also, bear in mind that if you are not using mod_perl, your CGI script,
and the Perl interpreter, will be read from disk for every request.
Unless reading that data file is time consuming for some reason (e.g. it
is huge, or remote), speeding it up may not improve the response time
for your HTTP request by very much.

HTH

-- 
Brian Raven 

Please consider the environment before printing this email.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.