posix_mq RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: ruby.posix.mq@librelist.org
Subject: Re: Listing existing queues
Date: Thu, 3 Mar 2011 22:49:00 +0100	[thread overview]
Message-ID: <AANLkTikQJRE5jjQBio9_RSzmpAXH3-GydjUX2MLDq7bV@mail.gmail.com> (raw)
In-Reply-To: 20110303213911.GA17845@dcvr.yhbt.net

2011/3/3 Eric Wong <normalperson@yhbt.net>:
> Yes.  However given the small number of POSIX message queue users and
> systems supporting it, I still see the feature as being in the early
> adopter phase and still has room to standardize on using the filesystem
> like Linux.
>
> And being early adopters of POSIX message queues, we (Ruby POSIX_MQ
> users/developers) have some ability to impact the standardizing of
> listing queues via the filesystem :)

Not sure if I understand you. Do you mean that, hopefully in a future
all the Linux/BDS systems will mount posix mqueues in the filesystem?
Some Linux kernels come without support for posix mq (not compiled).
Anyhow, assuming posix mq was widely adopted and extended, how could
we be sure that all the systems would use the same mount point?

Maybe I miss something, but I still think that a simple API funcion
"mq_list" which returns an array of char* representing each existing
mqueue name would be easier.

Cheers.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

  reply	other threads:[~2011-03-03 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 12:35 Listing existing queues Iñaki Baz Castillo
2011-03-02 19:38 ` Eric Wong
2011-03-03  5:08   ` Iñaki Baz Castillo
2011-03-03 21:39     ` Eric Wong
2011-03-03 21:49       ` Iñaki Baz Castillo [this message]
2011-03-03 22:02         ` Eric Wong
2011-06-21 13:03       ` Iñaki Baz Castillo
2011-06-21 18:24         ` Eric Wong
2011-06-22 20:09           ` Iñaki Baz Castillo

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

  List information: https://yhbt.net/ruby_posix_mq/

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

  git send-email \
    --in-reply-to=AANLkTikQJRE5jjQBio9_RSzmpAXH3-GydjUX2MLDq7bV@mail.gmail.com \
    --to=ibc@aliax.net \
    --cc=ruby.posix.mq@librelist.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/ruby_posix_mq.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).