From alsa-devel-owner@alsa.jcu.cz  Wed Feb 10 00:15:46 1999
Received: from post.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id AAA02064
	for <alsa-devel@alsa.jcu.cz>; Wed, 10 Feb 1999 00:14:46 +0100
Received: from [212.228.182.246] (helo=ariel.sr.home)
	by post.mail.demon.net with esmtp (Exim 2.12 #1)
	id 10AMMe-0007BC-00
	for alsa-devel@alsa.jcu.cz; Tue, 9 Feb 1999 23:14:44 +0000
Received: (from steve@localhost)
	by ariel.sr.home (8.8.7/8.8.7) id XAA05236
	for alsa-devel@alsa.jcu.cz; Tue, 9 Feb 1999 23:13:37 GMT
Date: Tue, 9 Feb 1999 23:13:37 GMT
From: Steve Ratcliffe <steve@parabola.demon.co.uk>
Message-Id: <199902092313.XAA05236@ariel.sr.home>
To: alsa-devel@alsa.jcu.cz
Subject: Client/port callbacks
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list


Jaroslav, Frank,

I have a question about the way snd_seq_client_callback_t is used.

There is one input routine per client along with a private data field.
Each port has its own private data.

Typically this input routine wants to use the private data belonging
to the destination port.  For example see event_input() in seq_midi.c.
This means that the client private data must also include pointers to
all the port private data structures.

It seems more natural for the sequencer core to pass the relevant port
private data to the input routine, and perhaps it would be even better
to also move the input routine from the client callbacks into the port
callbacks.

What do you think?

..Steve

