Greetings, During the last face to face we had a start of a discussion on what should fall within the scope of the PUSH specification. I feel we should go a little further on this matter.
As it is designed right now the whole system requires 3 APIs : - one between the web application and the browser (the core of this spec) - one between the push server and the application server - one between the push server and the device. During the face to face I think we agreed that the first two at the very least should fall within the scope of the spec, do we feel the third one is trivial enough to not require any sort of specification ? There are other parts that I also feel would require some attention: - How the push server is discovered and selected (currently the spec speaks of an intent server but with intent currently being shelved I am unsure whether this is the right path to take. Also it seemed to me that the user journey on proxy selection was rather different than the one imagined for web intents). - How a given application registers on the push server and how the push server may or may not allow access to its push service (I guess this falls within some of the security remarks and the general security model of the solution). - How the push server should be designed (I think we agreed that writing some informational guidelines that would be non normative would be a good idea). //Arnaud _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you.
