[dev] Content package is required?

[Michael J Rubinsky]

Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> Appears that way, and that shouldn't be the case.  An admin should  
>> be able to disable for, say, performance reasons.  (I have a client  
>> that wants exactly this.) Since I'm not familiar with the code, any  
>> pointers on the best place to do this?  Thoughts on config  
>> (conf.php) vs. Null driver vs. disabling package in registry.
>
> This is probably best done via a config switch, probably  
> per-application. Some applications absolutely require it (Trean is  
> one since it uses it as primary storage). A Null driver, or  
> disabling it in the registry probably wouldn't be a good overall  
> solution since we would still need to disable the UI components that  
> rely on it; It doesn't make any sense to allow input of tags when  
> they are not going to be persisted to storage. Of course, we can do  
> an additional check, in addition to the config switch, for Content  
> being available and disable the UI for either case.
>
> Another option is what Ansel does, it allows basic usage of tags but  
> disables the more resource intensive operations like tag browsing.

Another thing to consider is that Content was originally designed to  
be not just a repository of tags, but a general way of linking content  
between applications. No idea if/when any of this will come to  
fruition, but it's worth keeping in mind when implementing some way to  
turn it off. This would be another argument for turning it off  
per-application, as well as wording it as turning off tag  
functionality; There may be other, less resource intensive  
functionality implemented in the future.
-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5849 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/dev/attachments/20140207/764eacba/attachment.bin>