[sync] More on m600i

[Alex Masidlover]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Alex Masidlover <alex.masidlover at axiomtech.co.uk>:
>
>> I've tried simply adding it to the list of cases and setting    
>> $response and $synctype to sensible values RESPONSE_OK and    
>> ALERT_TWO_WAY. Unfortunately it fails at early on when it checks    
>> that $this->_targetLocURI has a valid database name, which it    
>> doesn't - I may be missing something but I can't find a member of    
>> SyncML_Command or SyncML_Command_Alert by that name.
>
> It may have been factored out - Karsten will have to weigh in here.

A quick and very dirty solution occured to me; what happens if Horde  
simply ignores the NEXT MESSAGE alert? I stuck a return in if the  
_alert matches ALERT_NEXT_MESSAGE and the m600i synchronises the  
calendar! Contacts has just come back with a 'too big' message but I  
think I can fix that by playing with the 50 byte margin that is  
applied to the MaxMsg size testing (will report back later on that).

>> I've also taken a look at the e-groupware changes to the SyncML    
>> implementation (which does have NEXT MESSAGE), however the changes   
>>  to Alert (and probably the rest) are pretty extensive and would    
>> probably take an expert in either Horde or eGroupware (or both) to   
>>  port across.
>
> This doesn't address your problem, but: Grrr! I was given every
> impression that the eGroupWare folks were going to contribute changes
> and fixes back to us. Care to poke them about that?

I'll try and politely request some help with the NEXT_MESSAGE issue  
quouting their offers to contribute back and see what happens.

Alex


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.