[dev] IMSP Package

Michael Rubinsky mike at theupstairsroom.com
Mon Jan 26 20:43:36 PST 2004


I finished my preliminary work getting my IMSP library code integrated as a 
horde/framework package.  Right now, it provides read/write access to IMSP 
address books and supports only Plaintext or CRAM-MD5 authentication. 
There are a few issues / problems that I still have to work on, but the 
core of the functionality is there.

To the maintainers - what is the best way for me to get the initial code to 
you?  In addition to a few patches for the pref changes and turba's 
sources.php there is a new package in horde/framework and new turba driver 
file.

Issues/General Notes:

-Tie in more completely with horde's logging and error reporting.

-The authorization code is still tied up in the 'core' of the Net_IMSP 
class and should probably be separated out as separate IMSP_Auth_? classes.

-The way IMSP servers handle distribution 'groups' is inherently different 
than the way turba handles them.  The display of the IMSP "groups" is 
disabled for now until I can fix the Turba_Driver_IMSP code to turn these 
into Turba_Lists.

-A preference was added to Horde's preferences for dealing with users who 
may have different logins for the IMSP server then for Horde.  If these 
preferences are set, they will be used...if they are blank, then the Horde 
login information will be used.  Right now, both fields (username and 
password) are visible text fields.  I would like to work on adding a new 
preference type, 'password', so that the form field will display as a 
password form field.

-The address book(s) that are used in turba are configured in the normal 
way (config/sources.php). The default is to use the login name as the name 
of the address book.  I am adding code that will automatically configure 
all the address books the user has at least read privileges on dynamically 
at login.

-Add a Net_IMSP_Options class and a Horde Prefs_IMSP class so the IMSP 
server can be used as a lightweight preference back-end.


Welcome all comments and suggestions...
Mike

--
Michael Rubinsky
TheUpstairsRoom Consulting




More information about the dev mailing list