Re: MIDIClientDispose and MIDIServer
Re: MIDIClientDispose and MIDIServer
- Subject: Re: MIDIClientDispose and MIDIServer
- From: Pete Gontier <email@hidden>
- Date: Mon, 06 Dec 2004 11:07:54 -0800
circa 12/4/04 2:51 PM, "Herbie Robinson" <email@hidden>
wrote:
>> At one point it probably crossed my mind to shutdown the server when the last
>> MIDIClient was disposed, but then I considered a client which is living in a
>> plugin or something like that. That plugin might come and go fairly
>> frequently, creating and destroying clients, and would in turn cause the
>> server to get launched and quit frequently. Since launching the server takes
>> a noticeable amount of time on all but the fastest machines with a minimal
>> set of drivers installed, that was probably the end of that.
> Actually, what's wrong with just leaving it up permanently, once somebody has
> used MIDI? It could be CHROOTed someplace harmless; so, it wouldn't be a
> security problem.
So far, I've assumed MIDIClientCreate is responsible for security, since
MIDIServer is an inaccessible implementation detail. If there are security
issues, they are bigger than my little helper app.
Because I am a helper app for a USB device which may well be plugged in
already at boot, I am concerned about being responsible for having launched
not just one but two immortal processes, with all the resources they imply.
Bertrand would disapprove. Instinct/intuition also tells me this would
create compatibility issues because not only would there be fewer fresh
invocations of MIDIServer and its plug-ins but the (first and) only
invocation would be a lot earlier than usual.
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden