On Tue, 24 Nov 2009, Jeff Trawick wrote:
As with mutex implementations, APR pollset implementations, or the
underlying OS support, are occasionally broken for some
configurations; the access to multiple implementations in APR 1.4.x
lends itself to allowing the user to specify a non-default pollset
implementation.
For example, the following could be used to work around the temporary
epoll sysdef confusion on Linux, or (cough) the port_getn() interface
challenges on Solaris:
Why am I feeling that figuring out which implementation of what works
or not should be done automagically, either by configure or at
startup?
Enabling all these user-choices might backfire with "Oh, you're
running foo on bar. But of course you know that you should fiddle with
the thingamajig, because we were too lazy to do a configure test".
I'm not being averse to tunability when it comes to selecting
implementations that performs better given somewhat equal
functionality, but when it's works-or-not I'd rather have the
dysfunctional alternatives weeded out and never exposed to the end
user...
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [email protected]
---------------------------------------------------------------------------
Raise electric eels-gain a lot of current popularity
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
