[ https://issues.apache.org/jira/browse/CB-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268428#comment-13268428
]
Patrick Mueller commented on CB-638:
------------------------------------
We probably should enable, *optionally*, and *not by default* being able to use the [WebView.addJavascriptInterface()|http://developer.android.com/reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,
java.lang.String)] API, instead of the current bridge.
It seems quite possible that this enablement would entail making a decision at runtime which
bridge to use, since the {{addJavascriptInterface()}} bridge will cause a trap on some simulators,
but work on devices running the same major/minor version of Android.
Having said that, most of these bridges are potentially huge bottlenecks anyway, across many
platforms. It might also be useful to think of some alternatives - like batching requests,
or something. It would might also be useful to try to lobby the platform developers to give
us some alternatives, like a [{{postMessage()}}|https://developer.mozilla.org/en/DOM/window.postMessage]
type of interface.
> Slow native bridge (especially android)
> ---------------------------------------
>
> Key: CB-638
> URL: https://issues.apache.org/jira/browse/CB-638
> Project: Apache Callback
> Issue Type: Improvement
> Reporter: Lee Crossley
>
> Doing many native callbacks (such as writing files) has a significant overhead.
> Trigger.io's native bridge is more than 5 times faster than Cordova (on Android). http://trigger.io/cross-platform-application-development-blog/wp-content/uploads/2012/02/chart_1-21.png
> I'd love to see similar performance stats in Cordova.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|