Hello! I found the code san.[h|cpp] code which implements notification parsing/generation. I'd like to discuss how this feature could be used in a SyncML client and (in the future) a server.
My original thought when looking at the spec was that SAN parsing/generation should be doable before starting and configuring a sync session. But that makes it difficult (if not impossible) to access the nonce that is needed for the SAN message. It is not possible to use SAN with a client yet, is it? At least I have no idea how to pass a SAN message content into the engine with the current API. If there was such an API, would the engine take the URI from the SAN message instead of from the local configuration that it was started with? Now for the server, based on which information does the server generate the SAN? We would have to start the server with its own local configuration, then define the URIs on a specific device that match with the ones configured on the server. Right? How is the mapping from textual MIME types to the binary MIME type numbers in the SAN handled? This looks like a serious limitation of the SAN format to me, because what number should be used for experimental MIME types which haven't been registered? -- 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. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
