[Kolab-devel] Is IMAP still the right choice?

[Gunnar Wrobel]

Quoting Thomas Koch <thomas at koch.ro>:

> Hi,
>
> I'll push regular updates to my bachelor thesis[1], if my Professor agrees.
> Right now I've pushed a list of advantages (short) and disadvantages  
> (long) of
> using IMAP for a groupware like Kolab does.[2]
>
> I've the impression that IMAP may have been a good, quick choice at the
> beginning of the project that should be revised now.

Revised for which specific reason?

>
> I'd like to propose as the subject of my bachelor thesis that I want to
> outline a groupware architecture with the following properties and  
> implement a
> small part of it:
>
> - restful protocols: portable contacts (now integrated in opensocial) and
> Google's calendar API v3[3]
> - NoSQL or plain files storage? CouchDB?
> - CardDAV / CalDAV to reach many clients
>
> I'd appreciate any comments on the IMAP subject or my "restful groupware"
> vision. Thank you!

I think I fail to see the link between being a "restful groupware" and  
the actual storage backend. As far as I know Kolab Systems is moving  
towards a more RESTful interface anyway. But that does not include  
changing the storage backend.

Cheers,

Gunnar

>
> [1] https://github.com/thkoch2001/bachelor-thesis
> [2] this link may change: http://thkoch2001.github.com/bachelor-
> thesis/multi/restful_groupwarese2.html
> [3] http://code.google.com/apis/calendar/v3
>
> Regards,
>
> Thomas Koch, http://www.koch.ro
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de