On Thu, 2008-01-24 at 12:34 +0000, Jonny Lamb wrote:
> Ha, MidaSync to the rescue again! Although that would be fairly cool,
> not only has a native pywbxml been started, but SyncEngine would need
> bindings to anything not in Python. I say that a native pywbxml is the
> way forward as then it can be thrown in the SyncEngine source and all we
> do is remove dependencies, not add them! \o/
>
> Thanks,
I like the idea of removing dependencies - however there is one issue
that is niggling in the back of my mind with a pure Python
implementation of wbxml. With a C/C++ implementation we can easily speak
wbxml from both native code and (through a thin layer) Python. With a
pure Python implementation we would have to rewrite in C/C++ if we want
to call from C++ (or have to call into Python which is a messy way to do
things).
So why may we want to go the other way? I am thinking of the pushmail
server. While sync-engine is fine as a pure Python implementation for
syncing, I am wondering about the scalability of a Python based pushmail
server if in an enterprise situation it is confronted with potentially
hundreds of concurrent connections. This may or may not be a problem, I
don't know at this stage but I would not want to make it more difficult
to develop something like libairsync.so should we need to.
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
