[Kroupware] Kroupware schedule and complement

[Helge Hess]

Martin Konold wrote:
>>>Kolab heavily uses imap, this is why it will scale so well.
>>Mozilla Calendar uses HTTP, this is why it does scale so well.
> 
> You definetly have a very valid point!
> 
> HTTP is scaling very well and is suitable to the task. The feature which makes 
> imap4 better scalable for groupware is that we do not want to retrieve always 
> the full calendar but we want to be a little bit more smart like scanning 
> headers only and beeing fully offline capable.

This does not conflict. Nothing speaks against addressing individual 
calendar items using http://.../mycal/62738.ics or something like this. 
HTTP URLs do not need to map to a physical file, a collection-resource 
like /mycal/ can easily be a database table which returns a full ics on 
GET and a partial ics if if a key is specified.

> compared to imap4 http is extremly simple and therefor we would need to use a 
> server side protocoll on top of http in order to gain the features we want.

Oh, oh, oh ;-) HTTP/1.1 isn't *that* simple if you implement the 
features which make it scalable (like persistent connections, e-tag 
based caching, etc).

Anyway, I didn't want to question the use of IMAP4 in Kolab, which is 
certainly suiteable, I just wondered why it was choosen above HTTP which 
already provides much better scalability infrastructure than IMAP4 (not 
implying that none exists for IMAP ;-).

Greetings
   Helge
-- 
__________________________________________________________________
Helge Hess                         Email:    helge.hess@skyrix.com
SKYRIX Software AG                 Tel:      +49-391-6623-0
Universitaetsplatz 12              Fax:      +49-391-6623-599
39104 Magdeburg, Germany           Internet: http://www.skyrix.com
__________________________________________________________________
Upgrade your SLEMS 3.x:              http://www.skyrix.de/de/news/
__________________________________________________________________