On Mon, Jun 11, 2001 at 01:26:09AM +0200, Sander Striker wrote: > About the apr_sms_get_features() suggestion: > It is the programmers job to find out _in advance_ if the > type of sms he is going to use will support what he needs. > Selecting a non locking sms in a multithreaded piece of > code would be wrong, for example :-)
:) later, a utility function, esp. when we get [_much_ later] a dso-eable sms loader, you could 'enumerate' the dsos and query them for their capability, at run-time. 'HO, APR! give me... range_locking! and threading-capable! and... shared-able-across-processes!' :) _much_ later. lukes
