> Thanks to everyone who replied! And thanks, Quanah, for your frank > assessment of this task. :-) I had no idea I was biting off more than I > could chew. I knew I'd have a (steep) learning curve for LDAP, but I guess > I thought the most obvious application for it would be to make an address > book for e-mail clients. Guess not! :-) > > So I'm now leaning towards just punting. My Plan B is to put all the data > into a SQL database, then have it periodically generate a flat, simple LDAP > directory suitable for use in Thunderbird and Outlook Express.
Store it in a database, but there is no reason for weird periodic syncronization. Just expose the database as LDAP via OpenLDAP's back-sql or Penrose. Consider using a real database like PostgreSQL (rather than MySQL) so you get triggers, stored procedures, full view support, etc... which makes the above much easier. > well as what fields both clients will use in address autocompletion. Adam, > your presentation (which was very helpful) mentioned a mHybrid schema, which > I found at http://www.whitemiceconsulting.com/node/53 . Does that cover > only Outlook and Evolution, or does it also cover Thunderbird? No, I consider the Thunderbird/Mozilla schema and address book to be so totally moronic as not to be worth the bother. On Windows one can configure WAB (Windows Address Book) to use LDAP, which is a better solution [I believe TB on Win32 can use WAB]. On UNIX the user has Evolution which is an unquestionably superior LDAP & IMAP client anyway. > Thanks again, all. I'm not totally sold on my Plan B, since LDAP is > probably still the "right" solution for storing my church's family > information, but since Thunderbird and OE are mainly what I want to support > (and since SQL/Perl/PHP etc. are already in my toolbox), I may just have to > go that route...
signature.asc
Description: This is a digitally signed message part
--- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
