[Tickets #2245] Horde Share implementation for Turba

[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=2245
-----------------------------------------------------------------------
 Ticket             | 2245
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Horde Share implementation for Turba
 Queue              | Turba
 Version            | HEAD
 State              | New
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2005-07-11 13:26) wrote:

> Thinking this through, this would break existing installations that 
> have permissions already set (other than max_contacts).  Should this 
> be implemented in such a way that it can coexist with the existing 
> permissions based system - maybe make it configurable on a per-source 
> basis whether to use Horde Perms or Horde Share?

How about letting Turba_Driver objects act like Share objects, or have a
getShare() method that would return a Share object that behaved like a share
but had the backend's permissions?

It's a little hard for me to suggest more without seeing your design, I
guess.