[Top] [All Lists]

RE: Border directories

2000-05-11 11:41:10
Unfortunately for your model, there are a variety of directory vendors which
do not store in either Berkeley DB or in a RDBMS datastore.  Microsoft is
one.  Novell another, Lotus a third.  There are others.  LDAP is certainly
less overhead than MAPI or what ever Novell's and Lotus's equivilent API
would be.  And LDAP is already built into the client to do exactly what you
are asking some one to write code to do.  Yes it can be done.  Yes it will
be done.  But most are doing this through LDAP for very good reasons.  Keep
in mind that many email clients do not do HTTP, so then you would have a
flow path of: to create s/mime email, don't create a new email in client,
open browser, browse to proper link, run query, have email aware http
application you have to now write create your email.  This application
should idealy call your default email package, but how will it tell Outlook
as an example about the certificate it just found?  I can't see that as a
natural flow of work.  Yes, if you are using an web based email service such
as hotmail.  No if you are using a corporate solution.


-----Original Message-----
From: pgut001(_at_)cs(_dot_)auckland(_dot_)ac(_dot_)nz 
Sent: Friday, May 12, 2000 6:33 AM
To: ietf-smime(_at_)imc(_dot_)org; pbaker(_at_)verisign(_dot_)com; 
Subject: RE: Border directories

"Walter Williams" <walter(_dot_)williams(_at_)genuity(_dot_)com> writes:

Last I checked, as the information is stored in a directory to
begin with,

Last I checked all the LDAP directories I could find used either
Berkeley DB or an RDBMS to store information.  With LDAP you have:

 client -> LDAP (client) -> LDAP (server) -> RDBMS

What I was suggesting is:

 client -> HTTP GET -> RDBMS

cutting out the superfluous LDAP bloat in the middle.


<Prev in Thread] Current Thread [Next in Thread>