[Tickets #4960] Re: Use horde.shares.turba.sourcename so Turba can use baseline Share driver

bugs at bugs.horde.org bugs at bugs.horde.org
Sun Jun 17 03:15:55 UTC 2007


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

Ticket URL: http://bugs.horde.org/ticket/?id=4960
-----------------------------------------------------------------------
 Ticket             | 4960
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Use horde.shares.turba.sourcename so Turba can use baseline Share driver
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Assigned
 Priority           | 3. High
 Owners             | Horde Developers, Chuck Hagenbuch
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2007-06-16 20:15) wrote:

> Right now Turba relies on custom attributes that we need to go away 
> for it to work with a generalized share driver. The fix as far as I 
> can tell is to use the source name as part of the group_uid instead 
> of as an attribute.

Mostly for my own benefit: this wasn't quite right. Turba relies on
hierarchical shares, meaning that the share ids carry way too much
meaning. It also relied on a number of custom share attributes. Both of
these prevent us from using a generalized, fast SQL share driver, for
example, and when it was a possibility for that driver to be written soon,
Turba needed its own code so it wouldn't break.

>From further looking, we're going to need some sort of 'params' key in any
future Share driver so that things like virtual address books can be stored
as shares and not require a separate database, so I'll be putting some
things back localized in that key. The list of attributes that share
backends will be required to store is:

owner
name
desc
params

(that doesn't include either "share name", which is really an id, or the
numeric id currently; this should be localized to one id value which isn't
carrying excess meaning so that the backend can assign it as necessary, and
it doesn't include permissions)



More information about the bugs mailing list