Re: LDAP or RDBMS?

[mark@mjwilcox.com]

It really will depend upon how many updates you are doing.
   As anyone will tell you LDAP is not really optimized for updates. 
But it could do what you want.

A secondary consideration could be, do you want to maintain this 
information so that it's available from multiple machines. If that's 
the case, then I'd recommend LDAP. If you only want to keep track 
of it on the machine itself, then I'd probably recommend a local 
DBM system (e.g. Berkeley or similar, not something like oracle or 
mySQL), because you don't want the overhead associated with 
doing network, etc.

Mark



On 10 Jan 00, at 22:54, Benjamin de los Angeles Jr. wrote:

> 
> Hello,
> 
> I'm planning to implement a timing system for users who login on terminal
> servers, such that a user is initially alloted a given amount of time and
> stored in a database (LDAP/RDBMS?).  And everytime the user logs out the
> "remaining time" is calculated and updated in the database.  Can LDAP
> handle this kind of updates efficiently or do I have to use an RDBMS just
> for this purpose?  Btw, I'm planning to authenticate to an LDAP server,
> it's just the "remaining time" that I'm really concerned about -- if I
> would add it as an attribute for a user in LDAP or create fields in RDBMS.
> 
> Thanks.
> 
> _
> Bench
> 
> 
>