On Tue, 1 Dec 2009, Patrick Ohly wrote:
This could be changed, but then we get into another problem: a
SyncML
server needs to know what kind of properties its client supports [1].
This is not the data conversion that you can do locally inside your own
application, it is for the conversion happening remotely.
Ok, now I understand the concept. On the O3SIS SyncML server, which is to
be integrated, this mapping is based on the manufacturer and model, as far
as I know.
This is purely theoretic at this point; real interoperability
testing
with servers and you backend would be needed to see whether such a
change and the corresponding server-side changes are necessary at all.
We'll start the heavy testing phase in a few days (or weeks), then we'll
see. As long as our application behaves like Evolution, everything should
be fine, as far as I understood.
Thanks for the explanation and the link to your article!
--
NEUE MOBILNUMMER: +43 660 4859550
Franz Knipp, Dipl.-Ing.
---------------------------------------------------------------------
knipp(a)m-otion.com
+43 660 4859550
https://www.xing.com/profile/Franz_Knipp
---------------------------------------------------------------------
m-otion GmbH
Favoritenstr 4-6/III, 1040 Wien
+43 1 205705 (Fax 99)
---------------------------------------------------------------------
www.m-otion.com