On Thu, Jul 19, 2001 at 11:07:52AM -0400, Fletch wrote:
> >>>>> "Anton" == Anton Berezin <[EMAIL PROTECTED]> writes:
> Anton> There should be some kind of canonical (for POE) way of
> Anton> just sitting there doing nothing waiting for signals.
>
> If you set an alias for the session it'll remain until the
> alias is removed. In what I've been doing I usually have a
> `main' session that's _signal state sends shutdown events to
> all the child sessions and itself (and its shutdown state
> removes the alias).
Thanks, I'll try that!
> Anton> And the reason to have a preforked server for me is that
> Anton> another truly asynchronous POE process talks to this
> Anton> server, but the server needs to do blocking calls (DBI).
> Anton> So in order to get a desired degree of concurrency I use
> Anton> pre-forking. Strictly speaking, this server is probably
>
> I've done exactly the same thing for the same reason (needing
> to do DBI calls so I start a couple of helpers with
> POE::Wheel::Run). /me wonders if any of the `popular'
> database APIs provide a way to make calls asynchronously, and
> if there might not be a way to get DBDs to sit on top of
> those. POE::Component::DBI would truly be most useful.
I agree wholeheartedly! I know that PosrgreSQL C API has means for
doing non-blocking queries. Apparently, most other database engines
have similar things. Unfortunately, I was only able to find *one*
thread discussing the usefulness of non-blocking DBI. It is dated 1998
and there was apparently nothing done since then. :-(
%Anton.
--
May the tuna salad be with you.
