[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         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Horde Share implementation for Turba
 Queue              | Turba
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2005-08-22 08:05) wrote:

> Does it really make sense to allow the users to create shared address 
> books for more than one backend? Most of them probably don't even 
> know what a backend is. It would make more sense to me if there is 
> only one backend providing the ability to share address books. Maybe 
> through a configuration option, like the client backend?

I agree with you about user's not really understanding about backends.  I
guess I just liked providing the ability for any driver to be able to use
shares...and in the case of backends like IMSP and possibly Kolab, the
changes made via Horde could be reflected in other clients the user might be
using.

Ah well, it does make sense though to have only one backend provide this to
avoid confusion.  How about in addition to a config option for which backend
should supply this we make one of the choices "Allow user to choose" or
something similar?  If you don't feel that makes sense either, I don't feel
*that* strongly about it...

As always, thanks for the feedback.