Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: Re: cloning snd_seq_t (or creating one from client id)
Date: Mon, 31 Mar 2014 23:01:19 +0200	[thread overview]
Message-ID: <5339D79F.8060502@ladisch.de> (raw)
In-Reply-To: <53397E54.2060309@tu-dresden.de>

Tobias Schlemmer wrote:
> ALSA imposes a policy
> that is obviously is not necessary from a technical point of view as
> every program instance can use different sequencer clients already with
> the current implementation at the cost of worsening the usability. My
> suggestion is to losen this restriction.

What you call "loosening this restriction" would actually involve
a nontrivial amount of code.

> P.S.: We are talking about the library API right?

Most of the client event handling is implemented in the kernel.

However, a threadsafe event (de)multiplexer could just as well be
implemented completely outside of the ALSA library.


Regards,
Clemens

      reply	other threads:[~2014-03-31 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  6:31 cloning snd_seq_t (or creating one from client id) Tobias Schlemmer
2014-03-31 12:29 ` Clemens Ladisch
2014-03-31 14:40   ` Tobias Schlemmer
2014-03-31 21:01     ` Clemens Ladisch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5339D79F.8060502@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox