From: Stephen Bennett <spb@gentoo.org>
To: "Joshua Brindle" <jbrindle@tresys.com>
Cc: "Karl MacMillan" <kmacmill@redhat.com>, <selinux@tycho.nsa.gov>,
"Stephen Smalley" <sds@tycho.nsa.gov>
Subject: Re: SELinux userspace infrastructure language
Date: Thu, 31 May 2007 20:45:02 +0100 [thread overview]
Message-ID: <20070531204502.3a667419@maya> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B01588BF0204@exchange.columbia.tresys.com>
On Thu, 31 May 2007 13:54:23 -0400
"Joshua Brindle" <jbrindle@tresys.com> wrote:
> Given all this I think C++ is the best bet, though I'm not adverse to
> most of the frontends being written in python, it would just be nice
> if the actual policy representation and accessors are available from a
> shared library API that most languages can use.
>From the library side, C++ has the advantage that it can produce
bindings for any language that C can. Writing a library in python
pretty much guarantees that noone will write anything using it in
anything but python, and on smaller systems the python interpreter can
get to be a lot of overhead.
Python for the frontend apps though is entirely reasonable -- it's
probably quicker to write, and people are unlikely to want to import it
into another application.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-05-31 19:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 17:35 SELinux userspace infrastructure language Joshua Brindle
2007-05-31 17:47 ` Karl MacMillan
2007-05-31 17:54 ` Joshua Brindle
2007-05-31 19:31 ` Karl MacMillan
2007-06-04 22:24 ` Karl MacMillan
2007-06-05 0:52 ` Joshua Brindle
2007-06-04 16:49 ` Karl MacMillan
2007-06-05 14:19 ` Stephen Smalley
2007-06-05 15:13 ` Karl MacMillan
2007-06-06 12:42 ` Stephen Smalley
2007-06-06 14:51 ` Karl MacMillan
2007-06-05 23:18 ` Joshua Brindle
2007-06-06 14:48 ` Karl MacMillan
2007-06-06 14:59 ` Joshua Brindle
2007-06-06 15:18 ` Karl MacMillan
2007-06-06 15:28 ` Joshua Brindle
2007-06-06 16:19 ` Stephen Bennett
2007-06-06 16:30 ` Karl MacMillan
2007-06-06 17:07 ` Stephen Bennett
2007-05-31 19:45 ` Stephen Bennett [this message]
2007-06-01 4:10 ` James Antill
2007-06-01 11:40 ` Stephen Bennett
2007-06-01 11:47 ` Stephen Bennett
2007-06-01 14:49 ` Karl MacMillan
2007-06-01 15:17 ` Joshua Brindle
2007-06-04 21:30 ` Help with semanage Hasan Rezaul-CHR010
2007-06-04 21:40 ` Stephen Smalley
2007-06-04 22:12 ` Hasan Rezaul-CHR010
2007-06-05 13:07 ` Stephen Smalley
2007-06-05 16:34 ` Hasan Rezaul-CHR010
2007-06-05 17:36 ` Stephen Smalley
2007-06-05 17:51 ` Stephen Smalley
2007-05-31 18:00 ` SELinux userspace infrastructure language Chad Sellers
2007-05-31 19:13 ` Karl MacMillan
[not found] ` <20070531205635.3b85f72b@maya>
[not found] ` <1180641092.22021.30.camel@localhost.localdomain>
[not found] ` <1180641428.22021.34.camel@localhost.localdomain>
2007-05-31 20:28 ` Stephen Bennett
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=20070531204502.3a667419@maya \
--to=spb@gentoo.org \
--cc=jbrindle@tresys.com \
--cc=kmacmill@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.