state-threads
[Top] [All Lists]

Re: IPC model

To: dmelomed@xxxxxxxx (Dan Melomedman)
Subject: Re: IPC model
From: mja@xxxxxxxxxxxxxxxxxxx (Mike Abbott)
Date: Mon, 21 May 2001 15:53:09 -0700 (PDT)
Cc: state-threads@xxxxxxxxxxx
In-reply-to: <20010520150722.A326@home.com> from "Dan Melomedman" at May 20, 2001 03:07:22 PM
Sender: owner-state-threads@xxxxxxxxxxx
> I am going to be using OpenLDAP 2.0.x libraries for now.
> Does this mean that a process could be potentially blocked, even though
> OpenLDAP does have asynchronous search functions?

That depends on whether OpenLDAP ever issues any blocking I/O calls,
whether to disk, network, or a pipe.

> If so, what would be
> an efficient and state-thread safe method of IPC, if I split the server
> into two (one being the POP3 server, the other being help processes that
> will accomplish LDAP authentication and return a response to a thread
> via IPC). I would also have the helper processes eventually do disk read
> I/O for the server.

Use the State Thread Library's I/O functions over a pipe or TCP socket
pair.  See
        http://oss.sgi.com/projects/state-threads/docs/notes.html#disk

If you port OpenLDAP to use the State Thread Library's I/O functions
instead of native functions (st_write instead of write on sockets) it
can run in the same process.  If it does disk I/O though the asymmetric
architecture performs better.
-- 
Michael J. Abbott        mja@xxxxxxx        www.repbot.org/mike

<Prev in Thread] Current Thread [Next in Thread>