From alsa-devel-owner@alsa.jcu.cz  Sat Aug 15 01:04:51 1998
Received: from obelix.fvdpol.inter.nl.net (frank@bd99-15.Breda.NL.net [193.79.246.240])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id BAA03148;
	Sat, 15 Aug 1998 01:04:05 +0200
Received: (from frank@localhost) by obelix.fvdpol.inter.nl.net (8.8.7/8.7.3) id BAA01271; Sat, 15 Aug 1998 01:03:55 +0200
From: Frank van de Pol <F.K.W.van.de.Pol@Inter.NL.net>
Message-Id: <199808142303.BAA01271@obelix.fvdpol.inter.nl.net>
Subject: Re: Raw and sequenced MIDI........
To: perex@jcu.cz (Jaroslav Kysela)
Date: Sat, 15 Aug 1998 01:03:54 +0200 (MET DST)
Cc: alsa-devel@jcu.cz (alsa)
In-Reply-To: <Pine.LNX.3.96.980813223153.865C-100000@entry.jcu.cz> from "Jaroslav Kysela" at Aug 13, 98 10:40:35 pm
Content-Type: text
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Jaroslav Kysela wrote:
> 
> Next idea: Shareable (device can be used by one or more clients) and
> exclusive (device can be used by one client only) open. Some application
> may requests by this 'don't merge events from others'.

OK, might be handy for some applications (eg. mod players that don't want
other applications to touch 'their' voices) 

> 
> Note for implementation: When application doesn't close used clients,
> sequencer must do this when close() on application's event queue occurs.

of course. That's why I'll keep track of which clients are using a port. On
client termination the sequencer's client manager can take care of releasing
ports (and releasing other data/resources bound to that client, like for
instance timers, queued events etc.).

Cheers,
Frank. 

+---- --- -- -  -   -    - 
|Frank van de Pol                  -o)
|F.K.W.van.de.Pol@inter.NL.net     /\\
|                                 _\_v
|Linux - Why use Windows, since there is a door?
|
|ALSA Sequencer: http://www.inter.nl.net/users/F.K.W.van.de.Pol/alsa/

