Can you add more information? The following keys are currently
defined:
description - a description of the peer in a format and
language that is understood by the user.
You are sending obexd stub, but we need something about the remote
OBEX peer, like the
id is set to BT MAC address + channel number, which could identify
the remote OBEX peer uniquely.
I was about to ask about the format when I saw you example below. Can
we make it slightly more machine readable, perhaps like this?
00:0A:94:03:EB:E5+16
Please put it into
On Thu, 2009-10-15 at 09:36 +0100, Zhao, Forrest wrote:
Thank you for update. Congwu has helped me to update to the right git
branch of syncevolution and libsynthesis yesterday. My status is: the
code for OBEX server/SyncML client binding is done; now I'm doing unit
testing. Will send out the
Patrick wrote:
Congwu mentioned that some workarounds were necessary in SyncEvolution
because the libsyncml test tool didn't set the message type correctly.
What exactly was the workaround - patch?
Two workarounds:
1) DEV_TYPE, why are we using desktop? Libsyncml is fairly stick on this and
does
On Thu, 2009-10-15 at 10:06 +0100, Chen, Congwu wrote:
Patrick wrote:
Congwu mentioned that some workarounds were necessary in SyncEvolution
because the libsyncml test tool didn't set the message type correctly.
What exactly was the workaround - patch?
Two workarounds:
1) DEV_TYPE, why are
Ohly, Patrick wrote:
On Thu, 2009-10-15 at 09:36 +0100, Zhao, Forrest wrote:
Thank you for update. Congwu has helped me to update to the right git
branch of syncevolution and libsynthesis yesterday. My status is: the
code for OBEX server/SyncML client binding is done; now I'm doing
unit
