destroying buckets and classes, terminating server loops

[Marcus Brinkmann]

Hi,

it seems there is no way to get rid of port buckets and classes.

The issue I am facing is that in the console client library, to make the
notify mechanism work, I have to put each notification request into its own
port bucket.  This is so that I can set the queue limit to a very low value,
and still receive notifications for different virtual consoles without
blocking (I have in mind here a client that displays more than one virtual
console simultaneously, or an optimization where a virtual console is
tracked a little longer after a switch in case the user switches back soon).

The natural thing to do this is to create a bucket and a service thread for
each virtual console connection.   But as virtual console connectionss are
started and destroyed (currently with every switch even), it's better to be
able to destroy the bucket and service thread when dropping the connection.

The only alternative to this I see is to keep a pool of empty buckets and reuse
them.  This might not be a bad idea anyway, as this would reduce the
overhead when switching the console.  So this might be what I do.

Anyway, I wondered if the lack of destructor functions for classes, buckets
and also the lack of a way to terminate the server loop has some important
reason or if there was just not a need for it before (as usual, I seem to
stretch the Hurd libraries beyond intended application :).

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de