[Tickets #12934] Re: Synchronization problem with Kronolith

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12934
------------------------------------------------------------------------------
  Ticket             | 12934
  Updated By         | rbe at tritem.net
  Summary            | Synchronization problem with Kronolith
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


rbe at tritem.net (2014-01-24 16:05) wrote:

Michael,

Thanks for this clear and fast analysis.

If you can find a workaroud for this problem, it will be great because  
i had already missed some meetings because they weren't not  
synchronized to my phone.
I'm now used to accept the meetings from horde but it's not the  
simpliest way (i also use a tablet, so 3 devices !!) and i often  
triple check the 3 calendars ...

I totally agree with you about the non respect of Microsoft own  
specifications and the frustration which comes with. Unfortunately,  
it's not the first time and i guess it won't neither be the last ...

Thanks again for your great work and support on Horde.
It really rocks.

Kind regards

Richard


> Outlook is sending an invalid response according to MS's own specifications.
>
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I  <MeetingResponse:MeetingResponse>
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I   <MeetingResponse:Request>
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I    <MeetingResponse:FolderId>
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I      @Calendar@
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I    </MeetingResponse:FolderId>
> 2014-01-24T11:12:17+01:00 DEBUG: [23761] I    <MeetingResponse:UserResponse>
> 2014-01-24T11:12:17+01:00 ERR: [23761] Unmatched end tag:
> 2014-01-24T11:12:17+01:00 ERR: Array
> (
>     [1] => 1
>     [2] => MeetingResponse:UserResponse
>     [4] => 1
> )
>
> 2014-01-24T11:12:17+01:00 ERR: Protocol Error
>
>
> According to the MS-ASCMD: 6.21 MeetingResponse Request Schema, the  
> UserResponse element comes before the FolderId element in a  
> <xs:sequence> block. Since it is arriving in an unexpected order,  
> the parsing fails. I can work around it in code since there is  
> really no technical requirement to have the response value before  
> parsing the folderid, other than the specs stating it must be in  
> that sequence.
>
> It's bad enough that different clients implement things so  
> differently, but when different versions of the same client do this  
> it is VERY frustrating.