[Tickets #6295] Re: Ansel flat shares with hierarchies

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6295
-----------------------------------------------------------------------
 Ticket             | 6295
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Ansel flat shares with hierarchies
 Queue              | Ansel
 Type               | Enhancement
-State              | Assigned
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2008-03-07 18:30) wrote:

Another issue that I came across while trying to see the best way to split
out the storage was that with your share driver, it is not possible to set
a scope other than Ansel unless a SQL table already exists for the scope
you want to use.   This might not be too big of an issue if the scope is
another Horde application, where the table might exist (if the new share
driver get's adopted) but it's not a great general solution.  Yes, the
table can always be created,  but I think one of the strong points of Ansel
is that you can use the API to create an image storage backend for any
custom application, not just Horde applications - and having to create a
new storage table in the Horde database for any new "application" is not a
very good solution IMO.