RE: [Phpgwtimetrack-developers] Contacts class LDAP

[Bob S. <bo...@pr...>]

Since my current plans call for providing an id to a contact
record inside the customer table, instead of having a customer
id linked inside the contacts table, this is probably not much
of a concern to me at this point. This is being done for 2 reasons:
1. To be more inline with the way Quickbooks works.
2. To lessen integration issues in regards to phpgw.

Bob

_____________________________
Bob Schader
CAD Systems Admin
Product Design Intl., Inc.
4880 36th St. SE, Suite 100
Grand Rapids, MI 49512
(616) 667-2600 x104

-----Original Message-----
From: php...@li...
[mailto:php...@li...]On Behalf
Of Miles Lott
Sent: Monday, March 19, 2001 12:16 AM
To: php...@li...
Cc: php...@li...
Subject: [Phpgwtimetrack-developers] Contacts class LDAP


The contacts class ldap backend is being written now.  So long
as you are using the contacts class for all read/write, it will
hopefully be transparent if you wish to change to ldap.
It is NOT yet useable.  FYI, the configs for this have been in
setup for a month or two, via config.php.

Since I know there will be debate about proper dn's etc.,
please take a moment to do the following if you are interested.
In current cvs addressbook, click the export button.  In the
dropdown will be a selection, 'phpgw LDIF'.  Select this,
uncheck the download button, and view the output in the browser.
Assuming you had some contacts entered, you should see the
proposed format for these entries.

I am nowhere near completing this, so it would be good to
comment on it now before we move too far.  Also note that
LDAP account dn's under ou=People or whatever would not be
affected by this.

-- 

Miles Lott - http://milosch.net
Handspring Visor USB and BeOS FS support for Linux
phpGroupWare - http://www.phpgroupware.org