[sync] More on m600i

[Alex Masidlover]

It looks like the m600i is failing to synchronise because of the Alert  
222 (NEXT MESSAGE) which, as I've spotted earlier on the list, is not  
implemented in Horde yet.

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.

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.

I'm failing to see how horde retains the name of the database that is  
being dealt with from when it gets a Sync command, it doesn't seem to  
have a place in the State/sync object.

Any help would be much appreciated.

Alex
-- 
Open Source Specialist
Axiom Tech Limited
W: http://www.axiomtech.co.uk
T: 0845 1270316 or +44 161 660 8009







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