On 12/6/12 16:08 , Mounir Lamouri wrote:
2. Discovery: some consumers seem to be inclined to use Web Intents to
discover other services. This is what Bryan Sullivan suggested for the
Push Notification API. When the Intent is invoked no action would
actually be taken, instead a URL is returned and then it's up to the
page to communicate with that URL with the Web Intent API no longer
involved.
JCD: Web intents does not provide discovery, but more like a directory
service.
Your proposal also provides registration and a sort of directory service,
even if you do not provide a matching algorithm.
So your proposal is more or less at the same level of functionality than
web intents in this respect.
3. Communication: you can use Web Intents to simply create a channel of
communication between APP A and APP B: you can easily specify which
service should be used to handle the intent and then, you can
communicate with it.
JCD: Web Intents also provides some isolation between the client and the
service.
Are you providing this isolation too ?
If your APP A and B can later establish a communication channel, it
seems not.
Yet that is a very appealing feature.
Best regards
JC
--
JC Dufourd
Directeur d'Etudes/Professor
Groupe Multimedia/Multimedia Group
Traitement du Signal et Images/Signal and Image Processing
Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France
Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144
