All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: LDAP vs Dbase semantics
Date: Fri, 20 Jan 2006 05:13:46 -0700	[thread overview]
Message-ID: <43D0D3FA.6090606@cornell.edu> (raw)
In-Reply-To: <43D0D0C0.7030603@cornell.edu>


> So.... that creates lots of problems. How do we handle modifications?
> We can fetch all the data in a local copy, work on it, then send it 
> back (ignoring the fact that the flush() operation might fail in an 
> irreversable way). That seems like a bad idea, because it eliminates 
> our ability to use the LDAP read optimizations. We're replacing a 
> server with some dumb local-store solution, like the linked list 
> thing, which is the worst data structure possible.
...but then again, do we care? This is a management library, not to be 
queried 100 times a second.
Maybe I should just put all the users in a linked list and be done with 
it...

Still doesn't solve the problem of what to do when flush() fails...


--
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.

      reply	other threads:[~2006-01-20 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 18:25 Seusers vs ldap Ivan Gyurdiev
2006-01-18 18:37 ` Daniel J Walsh
2006-01-18 21:13   ` Joshua Brindle
2006-01-20  8:52     ` Ivan Gyurdiev
2006-01-20 13:10       ` Joshua Brindle
2006-01-20 13:25         ` Ivan Gyurdiev
2006-01-20 12:00 ` LDAP vs Dbase semantics Ivan Gyurdiev
2006-01-20 12:13   ` Ivan Gyurdiev [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=43D0D3FA.6090606@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    /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.