On 15/02/2013 21:16, Andreas Dick wrote:
In my eys, OwnlCloud is a great frontend for calendars, addresses and files, similar what RC is for emails and addresses, but I would prefer a expanded RC frontend whit its own backends.... and then some extended backends for e.g. SabreDAV to access them via DAV from other clients. The reason is, that e.g. callendar and addressbooks over DAV is probably fast enough for mobile phones, but verrrry slow compared to e.g. the native addressbook of RC (SQL or LDAP)
Even phones will sync the answer locally, and work from cache. The same happens with the other "myroundcube" calendar plugin mentioned - it periodically syncs to the backend via dav and then works from database the rest of the time (same also with the carddav plugin, it just syncs to a copy of the existing contacts sql table)
The benefit of this design is that you can sync to multiple dav upstreams, eg pull public holidays in from some source, pull in your gmail contacts, pull in your office CRM contacts, etc.
However, I wanted something more tightly integrated with my DAV server (which I have picked OwnCloud/SabreDav for now), so I was looking at a straight plugin to RC to make its contacts read directly from the owncloud DB. So the two wouldn't sync, they would be tightly coupled via the DB. Plenty of disadvantages in this approach...
Ed W