qsos evaluation of "kolab"

I just found this:
http://ww
w.qsos.org/sheets/groupware/kolab/

Hmm, I disgree on some of their results.
E.g. IMAP you could consider a remote API...

-- 
Managing Director - Owner: www.intevation.net       (Free
Software Company)
Germany Coordinator: fsfeurope.org. Coordinator:
www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB
18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Op Thursday 07 February 2008 19:00:37 schreef Bernhard
Reiter:
> I just found this:
> http://ww
w.qsos.org/sheets/groupware/kolab/
>
> Hmm, I disgree on some of their results.
> E.g. IMAP you could consider a remote API...

You could, but it is not recognized as such (I think).  E.g.
SOAP is 
evaluated, and this is indeed recognized as  remote API. 
The report does not 
stated, for which purpose this remote API should be used. 
Is it to populate 
and to retrieve data from the server?  Wouldn't you call
ldap in that case 
the remote API?  However, I can imagine that people are more
familair with 
soap syntax than the ldap syntax.  So, yes I can imagine
that people expect 
an SOAP interface to be part of kolab.  Would that be hard
to add?  There is 
already an http server running, so that's not the problem. 
Now the 
problematic part is the conversion from and to the SOAP
structure to the ldap 
structure.  That would be a nice GSoC subject ;)

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Richard Bos <mlradoeka.nl> writes:

> Op Thursday 07 February 2008 19:00:37 schreef Bernhard
Reiter:
>> I just found this:
>> http://ww
w.qsos.org/sheets/groupware/kolab/
>>
>> Hmm, I disgree on some of their results.
>> E.g. IMAP you could consider a remote API...
>
> You could, but it is not recognized as such (I think). 
E.g. SOAP is 
> evaluated, and this is indeed recognized as  remote
API.  The report does not 
> stated, for which purpose this remote API should be
used.  Is it to populate 
> and to retrieve data from the server?  Wouldn't you
call ldap in that case 
> the remote API?  However, I can imagine that people are
more familair with 
> soap syntax than the ldap syntax.  So, yes I can
imagine that people expect 
> an SOAP interface to be part of kolab.  Would that be
hard to add? There is 
> already an http server running, so that's not the
problem.  Now the 
> problematic part is the conversion from and to the SOAP
structure to the ldap 
> structure.  That would be a nice GSoC subject ;)
>

This is basically just a debugging job as this is all
already being
delivered by Horde. WebDAV, SOAP, SyncML, ... it is all
there and just
needs someone checking if it works.

Cheers,

Gunnar

> -- 
> Richard Bos
> We are borrowing the world of our children,
> It is not inherited from our parents.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                         
Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users