Hi, On Wed, Sep 1, 2010 at 7:48 AM, Sateesh Kavuri <[email protected]> wrote: > > > On Tuesday 31 August 2010 09:49 PM, ext Luiz Augusto von Dentz wrote: >> >> Hi, >> >> On Tue, Aug 31, 2010 at 1:34 PM, Patrick Ohly<[email protected]> >> wrote: >> >>> >>> On Mon, 2010-08-30 at 23:06 +0100, Luiz Augusto von Dentz wrote: >>> >>>> >>>> OpenSync there is a plugin in obexd to support synchronization over >>>> obex, is there a plan to have such a plugin for buteo too? >>>> >>> >>> There's a feature request open: >>> http://bugs.meego.com/show_bug.cgi?id=3868 >>> >>> It's a bit unclear to me if and when that'll get implemented. >>> >> >> Well, I can implement it, Im not sure why you guys are pointing to >> meego bugs when meego is suppose to use what is upstream, that means >> buteo and obexd upstream must agree on what is best to do here, or is >> buteo suppose to be meego only? >> > > Right now, Buteo is MeeGo only. Maybe after sometime it can be made > available in other repos.
That is ok I guess, but note that by being MeeGo only it means that upstream project such as obexd will only get tested with Buteo when using MeeGo, so Buteo may loose some ground by not being widely adopted. Also Im not sure if you guys understand that obexd has to be qualified, afaik Buteo only support Nokia specific profiles so it never got qualified by any means, but if we decide to officially support irmc then we probably gonna need to pass pts tests. > Yes, obexd is used to serve capability files, but note that msyncd does not > have a direct dependency on obexd and it is also not required for some of > the > usecases, like online sync. Otherwise the syncml plugin uses libopenobex to > handle the communication with the peers. msyncd could depend on obexd, > but for that a separate plug-in has to be written that could pass on the > syncml messages between obexd and msyncd, which in my view is not a good > dependency. Also note that msyncd handles many other kinds of protocols > other > than syncml (MTP, for example). Well msyncd doesn't have a build dependency on obexd, but it does have a runtime dependency, which won't change by doing the connection handling in obexd. Im not sure what is the relevance of other protocols here, Im only saying that for OBEX protocols we already have a daemon doing the connection handling, one that was adopted by both Maemo and Moblin before Buteo was released. Note also that right now is completely impossible to do the usb cable detection right, because that will require us to open every tty which support OBEX protocol but we can't do this because some other daemons trying to open them too, so right the ports are hardcoded and I believe msyncd does have to do the same workaround. -- Luiz Augusto von Dentz Computer Engineer _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
