[Tickets #2360] NEW: Uniquely identify multiple IMSP sources internally, across all users

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2360
-----------------------------------------------------------------------
 Ticket             | 2360
 Created By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Uniquely identify multiple IMSP sources internally, across all users
 Queue              | Turba
 Version            | HEAD
 State              | New
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2005-07-30 11:28) wrote:

Have Turba provide a consistent, unique internal name (key into $cfgSources)
for each IMSP source that is dynamically made available.

Currently, Turba sequentially assigns the keys (IMSP_1, IMSP_2) etc... But
there is no guarantee that IMSP_3, for example will always point to the same
IMSP source.  It all depends on what other IMSP sources the user has access
to.  Fo instance, I have a IMSP addressbook called username.clients that I
want to use as the  "client addressbook" for my users. Currently, there is
no way of knowing what name to use in the client addressbook configuration,
since this is a dynamic source not available to all users.  For me it might
be IMSP_3, for another user it might be IMSP_2.

Having Turba assign a consistent, unique, and predictable id to each IMSP
source would solve this.

I've been meaning to get around to look at this for quite some time, now
that I've added the ticket, I might remind myself a little more often ;)