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.
The reason that Im asking this is because we did recently integrate
irmc (Sync) profile in obexd which we might use sync framework to get
the necessary information, so my hope is that we don't have to
duplicate code for handling obex connection when in fact we already
have a dedicated daemon doing that, obexd, in fact this should
simplify a lot the connection handling since all sync framework would
need to care is the syncml not obex and obviously obexd is already
doing connection handling for other obex targets.
What you describe is the design implemented in SyncEvolution and obexd
for Moblin. In the Buteo design, msyncd is the central daemon which
accepts incoming OBEX connections directly by calling libopenobex.
But it doesn't have to, actually msyncd already depend on obexd
anyway, since obexd handles other requests like capabilities request.
So my point is basically to use obexd (OBEX daemon) for what it is
for, handling OBEX connections, and leave msyncd to do the
synchronization, this should simplify the design.
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).
Regards,
--
Sateesh
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
