On Friday 23 November 2007, Mark Ellis wrote:
> On Wed, 2007-11-14 at 12:41 -0500, Paul Stanisci wrote:
> > > > Also, under "Base Install", should a sub page be created to explain
> > > > the difference between vdccm and odccm, and when to use each one? 
> > > > Should users of non-WM5 devices continue to use vdccm, or will it
> > > > soon be deprecated?
> > >
> > > Unless someone steps forward, we'll only document odccm, which has a
> > > legacy mode to support WM2003 users. We've considered it deprecated for
> > > some time and will probably move it to legacy/ in svn for 0.11...
> >
> > If odccm will handle WM2003 and WM5 users, I guess there is little point
> > to document and maintain old version of dccm. Though, the documentation
> > should state that old version of dccm exist and that the user should use
> > odccm instead.
>
> Just a quick comment on the vdccm/odccm stance. AFAIK raki won't work
> with odccm, not sure about the rest of synce-kde because I don't use it.
> It would be nice if someone could implement odccm's dbus interface in
> raki, unfortunately my C++ is not up to the task. An interim possibility
> I've considered is a dummy vdccm that sits between odccm and synce-kde,
> but again, because I use gnome it's at the bottom of my list.
Hi,
maybe we shall list all features of vdccm and odccm to compare them directly 
as i guess, that some  features of vdccm are missing in odccm and vice versa.

So for vdccm we have:
- Support for PocketPC 2003 devices
- Support for WM 5 devices
- Support for multiple devices simultaneously
- Support for SynCE-KDE (raki) and all of those tools which rely on 
  the "active_connection"-file in the ~/.synce/ directory
- Support of a socket-connection for controll-messages to and from other
  synce-tools (e.g. raki) like password-request and password-offer 
  messages, ...
- Connected devices can be identified either by their ip-addresses or by their 
  logical device-name.
- Acts as device-proxy for WM 5 devices mediating between the synce-tools and 
  the devices.

If someone can also list all features of odccm we are able to compare them 
helping deciding what should be declared depreciated or should be implemented 
either in vdccm or in odccm.

regards
voc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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

Reply via email to