>
> I am looking at this at the moment but there is a number of very
> significant fixups and improvements I need to make to sync-engine itself
> first. The Airsync stuff for pushmail is straightforward but is
> sufficiently different to the PIM syncing to require substantial changes
> to the way we handle the individual items. I had thought about giving
> the server a pluggable architecture with pluggable backends (e.g. imap,
> pop, local file database etc). One of those backends could be a plugin
> for Conduit....
>
> I'll probably do an IMAP backend first as this is the one I need :)
>
> The server would be fundamentally distinct from sync-engine (it would
> have to be at least initially to make debugging easier) and is designed
> to run stand-alone so that the mobile device can connect to it in the
> same manner as it would an Exchange server.
>
> Let's talk about this later next week on IRC. I need to finish the
> updates (DTPT, partnership and config stuff) to sync-engine first and I
> should be able to get back to the push server then.
Sounds good. If its relatively light on dependencies I think a conduit
backend would be born very quickly :-) As you know I will be about quite a
bit :-D
John
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
