On 05/19/2013 11:20 AM, Ján Máté wrote:
Hi all,
we have a good news for you :-)
CalDavZAP 0.9.0 release candidate 3 - biggest changes since the rc2:
- fixed TON of bugs related to new Todo interface (especially Apple related) ... many thanks for your bug reports!
- added globalIgnoreCompletedAlarms option
- updated jQuery to 2.0.0
- updated jQuery-UI to 1.10.3
- Hungarian localization
http://www.inf-it.com/CalDavZAP_0.9rc3.zip
demo: http://www.inf-it.com/caldavzap-next/ changelog: http://www.inf-it.com/caldavzap-next/changelog.txt
CardDavMATE 0.11 release candidate 3 - biggest changes since the rc2:
- this version works well with THOUSANDS of contacts (previous versions was very slow with more than several hundreds of contacts)
- updated jQuery to 2.0.0
- updated jQuery-UI to 1.10.3
http://www.inf-it.com/CardDavMATE_0.11rc3.zip
demo: http://www.inf-it.com/carddavmate-next/ changelog: http://www.inf-it.com/carddavmate-next/changelog.txt
Both releases are very stable (installed on our production servers). If nobody reports any problem in ~1-2 weeks we will update few missing translation strings and will release the next public version of both clients.
Just started testing this release, and found the following PROPFIND request:
<?xml version="1.0" encoding="utf-8"?><D:propfind xmlns:x3="http://apple.com/ns/ical/" xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop>x3:calendar-color/<D:current-user-privilege-set/><D:max-image-size xmlns:Dd="urn:ietf:params:xml:ns:carddav"/><D:displayname/><D:resourcetype/><D:supported-report-set/><B:supported-calendar-component-set xmlns:B="urn:ietf:params:xml:ns:caldav"/><B:supported-calendar-component-sets xmlns:B="urn:ietf:params:xml:ns:caldav"/><D:sync-token/></D:prop></D:propfind>
- You declare the caldav namespace globally (prefixed by 'C'), but then you redeclare it locally in supported-calendar-component-set (prefixed by 'B'). This is confusing my server (which is a bug on my part), but it seems to be extra unnecessary bits on the wire.
- There is no standard caldav property named supported-calendar-component-sets (plural). Are you expecting this from some server or is it a typo? v0.9rc3 isn't showing any of my calendars and I'm wondering if this is the reason.
Hi Ken,
On May 19, 2013, at 7:51 PM, Ken Murchison murch@andrew.cmu.edu wrote:
Just started testing this release, and found the following PROPFIND request:
<?xml version="1.0" encoding="utf-8"?><D:propfind xmlns:x3="http://apple.com/ns/ical/" xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><x3:calendar-color/><D:current-user-privilege-set/><D:max-image-size xmlns:Dd="urn:ietf:params:xml:ns:carddav"/><D:displayname/><D:resourcetype/><D:supported-report-set/><B:supported-calendar-component-set xmlns:B="urn:ietf:params:xml:ns:caldav"/><B:supported-calendar-component-sets xmlns:B="urn:ietf:params:xml:ns:caldav"/><D:sync-token/></D:prop></D:propfind>
- You declare the caldav namespace globally (prefixed by 'C'), but then you redeclare it locally in supported-calendar-component-set (prefixed by 'B'). This is confusing my server (which is a bug on my part), but it seems to be extra unnecessary bits on the wire.
you are right - we will simplify the request in the 0.9 final
- There is no standard caldav property named supported-calendar-component-sets (plural). Are you expecting this from some server or is it a typo? v0.9rc3 isn't showing any of my calendars and I'm wondering if this is the reason.
interesting, because Apple asks for the same property, from iOS 6.0.3 request:
<?xml version="1.0" encoding="UTF-8"?> <A:propfind xmlns:A="DAV:"> <A:prop> ... <B:supported-calendar-component-set xmlns:B="urn:ietf:params:xml:ns:caldav"/> <B:supported-calendar-component-sets xmlns:B="urn:ietf:params:xml:ns:caldav"/> ... </A:prop> </A:propfind>
but you can safely remove it from the request because currently we don't use the result (we forgot to remove it when we tested our client) ... we will remove it too in the final 0.9
It if is possible please send me a private e-mail with some testing credentials to your server and we will check where is the problem.
JM
Hi Ken,
XML requests cleanup patches for RC3 (for CardDavMATE there are also few very minor changes):
http://www.inf-it.com/fixes/caldavzap_0.9rc4x.diff http://www.inf-it.com/fixes/carddavmate_0.11rc4x.diff
Please report whether these patches solve your problem.
JM
On May 19, 2013, at 7:51 PM, Ken Murchison murch@andrew.cmu.edu wrote:
Just started testing this release, and found the following PROPFIND request:
<?xml version="1.0" encoding="utf-8"?><D:propfind xmlns:x3="http://apple.com/ns/ical/" xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><x3:calendar-color/><D:current-user-privilege-set/><D:max-image-size xmlns:Dd="urn:ietf:params:xml:ns:carddav"/><D:displayname/><D:resourcetype/><D:supported-report-set/><B:supported-calendar-component-set xmlns:B="urn:ietf:params:xml:ns:caldav"/><B:supported-calendar-component-sets xmlns:B="urn:ietf:params:xml:ns:caldav"/><D:sync-token/></D:prop></D:propfind>
You declare the caldav namespace globally (prefixed by 'C'), but then you redeclare it locally in supported-calendar-component-set (prefixed by 'B'). This is confusing my server (which is a bug on my part), but it seems to be extra unnecessary bits on the wire.
There is no standard caldav property named supported-calendar-component-sets (plural). Are you expecting this from some server or is it a typo? v0.9rc3 isn't showing any of my calendars and I'm wondering if this is the reason.
-
Ján Máté -
Ken Murchison