On Mon, 2009-09-28 at 09:04 +0100, Lukas Zeller wrote:
Hi Patrick,
On Sep 27, 2009, at 22:39 , Patrick Ohly wrote:
> The device ID of the server is typically the sync URL (which can be
> guessed, as described in another mail) [...]
Which ID are we talking about?
As a first approximation, the Server ID that is placed in the SAN
message to a client. My understanding is that in order to get phones to
work with a "personal SyncML server", this string must match something
that is recognized by the phone ("PC Suite").
Now perhaps it then doesn't matter what the server sends in its LocURI
and the devInf, but the wording in the SAN spec is pretty fuzzy about
this.
> [...] but in some cases (OBEX) also some other kind of string
which
> cannot be guessed.
What kind of string would it be for OBEX? And does it have any
significance then?
I'm not sure whether it is relevant. I guess we'll find out once we try
it with phones.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.