From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Joshua Brindle <jbrindle@tresys.com>,
selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Add a few direct dbases to handle
Date: Fri, 14 Oct 2005 16:45:43 -0400 [thread overview]
Message-ID: <435018F7.6070706@cornell.edu> (raw)
In-Reply-To: <435017B2.7040107@cornell.edu>
>
>> I thought we agreed to have a direct only accessible part of the
>> handle, such as
>>
>> struct semanage_direct_handle {
>> semanage_handle_t *handle;
>> /* direct stuff goes here */
>> };
To put it another way.. this "direct-only" part does exist, but it's
hidden away.
(into dbase_config_t -> dbase), which is an interface type. Then the
method table
(dbase_config_t->dtable) specifies how to access it, which is equivalent
to your
function table for modules.
In fact, I want to convert your modules functions into a database too, but
I haven't gotten to it yet, and this isn't high priority.
So...basically I have multiple backend-specific portions, distributed by
functionality,
rather than putting it all into one big table of function pointers that
aren't related.
--
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:[~2005-10-14 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 18:16 [ SEMANAGE ] Add a few direct dbases to handle Ivan Gyurdiev
2005-10-14 18:39 ` [ SEMANAGE ] Bugfix previous patches Ivan Gyurdiev
2005-10-14 20:08 ` Stephen Smalley
2005-10-14 20:20 ` [ SEMANAGE ] Add a few direct dbases to handle Joshua Brindle
2005-10-14 20:40 ` Ivan Gyurdiev
2005-10-14 20:45 ` Ivan Gyurdiev [this message]
2005-10-14 20:39 ` Joshua Brindle
2005-10-14 20:59 ` Ivan Gyurdiev
2005-10-14 21:06 ` Joshua Brindle
2005-10-14 21:40 ` Ivan Gyurdiev
2005-10-15 11:34 ` Ivan Gyurdiev
2005-10-15 11:38 ` Ivan Gyurdiev
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=435018F7.6070706@cornell.edu \
--to=ivg2@cornell.edu \
--cc=jbrindle@tresys.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.