[Tickets #6653] Re: File based preference driver

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6653
-----------------------------------------------------------------------
 Ticket             | 6653
 Updated By         | thomas.jarosch at intra2net.com
 Summary            | File based preference driver
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


thomas.jarosch at intra2net.com (2008-04-29 04:07) wrote:

Here are some advantages compared to sqlite:

- Loose coupling if you integrate it with another system:
  Easy delete/rename/restore/backup of user preferences
  as prefs are stored as /some/where/##USERNAME##.prefs.
- Scalability: Using sqlite, two or more processes cannot write
  to the same database at the same time. You either busy wait
  or get a timeout in the worst case. No worries with the file based
prefs.
- Speed should be equal or faster, but preference data is usually
  very small, so that shouldn't be taken into account.
- We had two cases of corrupted sqlite databases in the past.
- No external dependencies

The /var/horde/prefs thing was just a default value to output an
error message in the log. I'll change that to PEAR_Error if you want.
Though I don't know how the preference subsystem likes me if I do this...