Calgo / Dav resources merge ?

[Grégory Oestreicher]

Hi all,

After some work done on a GroupDAV / CalDAV resource and a commit in
playground I was pointed on IRC to the Calgo resource, which implements
GroupDAV support.

I've clearly made a mistake here by not checking on this list earlier, or at
least announcing that some work was going on on my side since some time.
Hopefully it is not too late to begin a merge of both resource, so let's begin
by a little comparison, from my point of view at least.

For the plus side, that may help merging, both resources use a class that
talks to the DAV backend : KGroupDAVProxy for Calgo and davAccessor for Dav.
Now the drawback is that KGroupDAVProxy speaks only GroupDAV while davAccessor
is meant to be subclassed to talk GroupDAV or CalDAV (and work will begin for
CardDAV, but I'm still digesting the IETF draft).

Another thing that is nice with KGroupDAVProxy is that it is thread-safe,
while davAccessor and subclasses are not. Though this have never been an issue
in my tests, some day sheer luck won't be enough.

I am open to discussion about the better ways to merge both works and make the
best *DAV resource :)

Cheers,
Grégory
_______________________________________________
KDE PIM mailing list kde-pim@...
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[Marco Nelles-2]

Hi,


I'm Marco, the developer of Calgo (promoted by credativ GmbH, Germany).
GroupDAV support works quite stable for now.

This little project Calgo should be the first step on the way to a full CalDAV
resource Calgo 2. So it is a quite positive surprise for me, that someone
already is working on this. Of course we can cooperate in order to produce the
best dav resource :-)

You've written, you've commited your resource to playground.
I will have a look at your code within the next few days in order to have an
overview and decide what might be the best way to proceed.

I personally welcome a cooperating!


Best regards,

Marco


Am Samstag 07 November 2009 12:14:33 schrieb Grégory Oestreicher:

> Hi all,
>
> After some work done on a GroupDAV / CalDAV resource and a commit in
> playground I was pointed on IRC to the Calgo resource, which implements
> GroupDAV support.
>
> I've clearly made a mistake here by not checking on this list earlier, or
>  at least announcing that some work was going on on my side since some
>  time. Hopefully it is not too late to begin a merge of both resource, so
>  let's begin by a little comparison, from my point of view at least.
>
> For the plus side, that may help merging, both resources use a class that
> talks to the DAV backend : KGroupDAVProxy for Calgo and davAccessor for
>  Dav. Now the drawback is that KGroupDAVProxy speaks only GroupDAV while
>  davAccessor is meant to be subclassed to talk GroupDAV or CalDAV (and work
>  will begin for CardDAV, but I'm still digesting the IETF draft).
>
> Another thing that is nice with KGroupDAVProxy is that it is thread-safe,
> while davAccessor and subclasses are not. Though this have never been an
>  issue in my tests, some day sheer luck won't be enough.
>
> I am open to discussion about the better ways to merge both works and make
>  the best *DAV resource :)
>
> Cheers,
> Grégory
> _______________________________________________
> KDE PIM mailing list kde-pim@...
> https://mail.kde.org/mailman/listinfo/kde-pim
> KDE PIM home page at http://pim.kde.org/
>

_______________________________________________
KDE PIM mailing list kde-pim@...
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[Grégory Oestreicher]

Hi Marco,

Le samedi 07 novembre 2009 13:02:08, Marco Nelles a écrit :
>
> I'm Marco, the developer of Calgo (promoted by credativ GmbH, Germany).

Nice to read from you.

> GroupDAV support works quite stable for now.

Great. Did you had the occasion to test it with Egroupware ? I'm trying to find
out why modification of an event from Korganizer "deletes" item on the backend.
As far as I can see this seems related to the fact that the ATTENDEE entry in
the iCal data received by itemChanged() lacks the X-EGROUPWARE-UID attribute,
but any information will be good.

And did you noticed issues to delete events when using https ? I'm asking
because that's the case for me and if it works for you I'm afraid that I may
have misdagniosed the source (see http://reviewboard.kde.org/r/2077/).

> This little project Calgo should be the first step on the way to a full
>  CalDAV resource Calgo 2.

Do you already have some development plans that you can share ? The
development of CalDAV should be easier now that the REPORT HTTP query is
supported in KIO. I'm also having a TODO item to add support for the
MKCALENDAR query, as defined in RFC 4791, but anyone interested can add this.

> You've written, you've commited your resource to playground.
> I will have a look at your code within the next few days in order to have
>  an overview and decide what might be the best way to proceed.

Nice, I'm waiting to have some news from you.

Please note that development is still going on on my side so the code may have
changed. I'm planning to add support for contacts in GroupDAV and this will
certainly result in a big refactoring to put all GroupDAV specific code in a
base class. Then CardDAV support will certainly have the same effect.

Cheers,
Grégory
_______________________________________________
KDE PIM mailing list kde-pim@...
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[Marco Nelles-2]

Am Samstag 07 November 2009 15:07:00 schrieb Grégory Oestreicher:

> Hi Marco,
>
> Le samedi 07 novembre 2009 13:02:08, Marco Nelles a écrit :
> > I'm Marco, the developer of Calgo (promoted by credativ GmbH, Germany).
>
> Nice to read from you.
>
> > GroupDAV support works quite stable for now.
>
> Great. Did you had the occasion to test it with Egroupware ? I'm trying to
>  find out why modification of an event from Korganizer "deletes" item on
>  the backend. As far as I can see this seems related to the fact that the
>  ATTENDEE entry in the iCal data received by itemChanged() lacks the
>  X-EGROUPWARE-UID attribute, but any information will be good.

No, eGroupWare has not being tested yet. Due to my company it has to work with
Citadel, so this is the focus by now.
So it maybe more correct, if I say it works with Citadel quite stable for now.

>
> And did you noticed issues to delete events when using https ? I'm asking
> because that's the case for me and if it works for you I'm afraid that I
>  may have misdagniosed the source (see http://reviewboard.kde.org/r/2077/).

No, I'm afraid https was until now not been tested. I will check this.

>
> > This little project Calgo should be the first step on the way to a full
> >  CalDAV resource Calgo 2.
>
> Do you already have some development plans that you can share ? The
> development of CalDAV should be easier now that the REPORT HTTP query is
> supported in KIO. I'm also having a TODO item to add support for the
> MKCALENDAR query, as defined in RFC 4791, but anyone interested can add
>  this.

No, everything I do is up on playground.

>
> > You've written, you've commited your resource to playground.
> > I will have a look at your code within the next few days in order to have
> >  an overview and decide what might be the best way to proceed.
>
> Nice, I'm waiting to have some news from you.

I think tomorrow I have time to look at your code. I will tell you.

>
> Please note that development is still going on on my side so the code may
>  have changed. I'm planning to add support for contacts in GroupDAV and
>  this will certainly result in a big refactoring to put all GroupDAV
>  specific code in a base class. Then CardDAV support will certainly have
>  the same effect.

Okay.


Best regards,

Marco
_______________________________________________
KDE PIM mailing list kde-pim@...
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/