[sync] More on m600i

[Chuck Hagenbuch]

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.

> 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?

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris