Hi Mounir,
Sorry for very late response.
I reviewed your Inter App Communication API[1] and I felt that the
intention of the API is similar to mine.
As described in the TODO list, the API should provide origin-based
filtering for both the caller and the receiver. It might be better if
the caller can specify the receiver directly.
I'm not sure that the new API is best solution for our purpose. There
already exists navigator.registerProtocolHandler and WebActivity, and
WebActivity is still young. Why not extend it?
[1] https://wiki.mozilla.org/WebAPI/Inter_App_Communication
Junichi
On H.25/05/03 22:54, Mounir Lamouri wrote:
On 02/05/13 13:59, Stefan Arentz wrote:
On 2013-05-02, at 2:19 AM, Junichi Hashimoto <ju-hashim...@kddilabs.jp> wrote:
These issues are solved if WebActivity has an option to set the receiver
when it is invoked and has the sender information when it is passed to
the receiver. As the identity for the option and the information
manifest URL seems suitable. I don't think to make another API for the
above purpose. To keep existing codes working the functionality should
be provided as an option.
Isn't this also how Android works? I think there are three things that can
happen on Android:
1) If you start an activity and there is only one application registered to
handle that activity, that app is chosen and started without user interaction.
Web Activity should have a security layer on top of that behaviour: only
certified applications (or privileged too?) should be allowed to
automatically handle an activity unless the user explicitly asked for
that application to be the default handler.
2) If you start an activity and there are multiple applications registered to
handle that activity, the user is given a choice to choose the application and
also to mark the application as default. If the default is set then Android
will not ask you in the future.
Web Activity should indeed behave that way too.
3) If you start an activity and you send it to a specific application (by its
bundle id) then that the activity is passed to that app without user
interaction.
This is something that I believe shouldn't happen with Web Activity.
Android Intents also allow you to know the list of applications able to
handle a specific activity. That's not something we want, right?
A few weeks ago, I drafted an Inter App Communication API. This API has
a ton of security issues we should solve before implementing anything
but would such an API work for your use cases Hashimoto-san?
Cheers,
--
Mounir
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
