On Thu, 2009-07-30 at 17:38 +0100, Beat Forster wrote: > >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. > Our PDA clients have integrated it already. > For the server side we have a separate > application called "pushalerter". There are > currently no plans to integrate into the server's > code, as not the SyncML server initiates it, but > the "outside world".
Yes, that makes more sense to me too. That means we would need to expose the SanPackage class to that outside world. Can it be moved into the SDK? > >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. > That is in fact an unsolved problem. We heard > from Symbian, that they are using a hardcoded > nonce. Our client simply ignores it, as far as I > remember. > After a first successful session, the last nonce could/can be used. Only if the outside world has access to it. Simply ignoring it looks easier. > >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? > Isn't 0 the unknown type ? I'll have to check it again. Not sure. Looks like that field can be ignored, like the nonce. -- 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
