« Return to Thread: Synthesis open source, provides data conversion (kind of)
Re: Synthesis open source, provides data conversion (kind of)
by Jelle de Jong
::
Rate this Message:
Patrick Ohly wrote:
> Hello!
>
> You might have seen the news on LWN.net:
> http://lwn.net/Articles/333059/rss
> http://lwn.net/Articles/333157/rss
>
> Synthesis, a commercial implementation of SyncML client and server
> technology, is now open source (LGPL). SyncEvolution, originally my
> spare time project, has been my full-time job at Intel since the
> beginning of this year. Part of that work was the migration of
> SyncEvolution to Synthesis and preparing this launch with them.
>
> We couldn't talk about this publicly for a long time, much longer than I
> had hoped, because of various legal issues and approvals that had to be
> sorted out. However, we contacted Daniel and Michael in January and
> discussed collaboration opportunities. My participation on the list
> about data conversion aspects was a result of that.
>
> However, I'm still not sure what OpenSync really is going to do
> regarding data conversion and how much the source code in libsynthesis
> will help. I also don't have time to participate in further discussions,
> so I'm afraid all that can be offered at this time is the invitation to
> look at the source code and provide patches if you need additional APIs.
> Currently, data conversion is tied into a sync session context and using
> it is not as easy as it could be (see sysync::DataConversion() for a
> starting point).
>
> Obviously, SyncEvolution+Synthesis cover some of the same aspects as
> OpenSync (modular backends to access local data, could be turned into a
> server). The way I see it, OpenSync and SyncEvolution+Synthesis are
> moving towards the same goal from different directions: OpenSync
> starting with the architecture and implementing more and more parts of
> it, SyncEvolution+Synthesis starting from the code and adding features.
>
> Because there is clearly urgent demand for it, we have to look at adding
> the server mode to SyncEvolution+Synthesis and cannot wait for OpenSync
> to fill that space. It's also less work for us to take that route.
>
I am wondering, all this talk about a server and client systems with
SyncML in this topic, how does this relates to the four bug reports
posted in the one bug report found here:
http://www.opensync.org/ticket/1073
Best regards,
Jelle de Jong
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
> Hello!
>
> You might have seen the news on LWN.net:
> http://lwn.net/Articles/333059/rss
> http://lwn.net/Articles/333157/rss
>
> Synthesis, a commercial implementation of SyncML client and server
> technology, is now open source (LGPL). SyncEvolution, originally my
> spare time project, has been my full-time job at Intel since the
> beginning of this year. Part of that work was the migration of
> SyncEvolution to Synthesis and preparing this launch with them.
>
> We couldn't talk about this publicly for a long time, much longer than I
> had hoped, because of various legal issues and approvals that had to be
> sorted out. However, we contacted Daniel and Michael in January and
> discussed collaboration opportunities. My participation on the list
> about data conversion aspects was a result of that.
>
> However, I'm still not sure what OpenSync really is going to do
> regarding data conversion and how much the source code in libsynthesis
> will help. I also don't have time to participate in further discussions,
> so I'm afraid all that can be offered at this time is the invitation to
> look at the source code and provide patches if you need additional APIs.
> Currently, data conversion is tied into a sync session context and using
> it is not as easy as it could be (see sysync::DataConversion() for a
> starting point).
>
> Obviously, SyncEvolution+Synthesis cover some of the same aspects as
> OpenSync (modular backends to access local data, could be turned into a
> server). The way I see it, OpenSync and SyncEvolution+Synthesis are
> moving towards the same goal from different directions: OpenSync
> starting with the architecture and implementing more and more parts of
> it, SyncEvolution+Synthesis starting from the code and adding features.
>
> Because there is clearly urgent demand for it, we have to look at adding
> the server mode to SyncEvolution+Synthesis and cannot wait for OpenSync
> to fill that space. It's also less work for us to take that route.
>
I am wondering, all this talk about a server and client systems with
SyncML in this topic, how does this relates to the four bug reports
posted in the one bug report found here:
http://www.opensync.org/ticket/1073
Best regards,
Jelle de Jong
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
« Return to Thread: Synthesis open source, provides data conversion (kind of)
| Free embeddable forum powered by Nabble | Forum Help |
