isn't that a perfect job for a unix domain socket? you can chmod(2) it (or use umask(2) before socket(2)), you accept(2) a connection from a client, read(2) a request, write(2) the reply and close(2) it or keep it open, just like with your two fifos. a socket behaves just like a fifo that works both ways.
I commited now a version with unix domain sockets. If the xml-file is in the cache the module can parse up to 1.000 parameters per second (see make test). The problem is that we need for a simple submenu up to 110 parameters (27 for access control). Perhaps I should remove all the debugging statements. BTW how expensive is a call to a subroutine compared with a simple if-statement in Perl (there is a function debug).
I have a PIII with 256 MB RAM (with KDE etc.). So it's not an ideal server today.
Michael -- ------------------------------------------------------------------- Michael Bell Email: [EMAIL PROTECTED] ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482 (Computing Centre) Fax: +49 (0)30-2093 2704 Humboldt-University of Berlin Unter den Linden 6 10099 Berlin Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
