On 8 October 2015 at 09:23, Wei, Xiaosong <xiaosong....@intel.com> wrote:
>
> Developer need to host XWalkRuntimeLib.apk for different CPU architectures,
> the URL will be appended with a query string “?arch=CPU_ABI” when the request
> is sent to server, where CPU_ABI is exactly the same as the value returned
> from “adb shell getprop ro.product.cpu.abi”, e.g, x86 for x86 32bit,
> armeabi-v7a for ARM 32bit.
>
Two comments about this:
1 - What about namespacing the manifest field, e.g.
<meta-data android:name=”org.xwalk.runtime”
android:value=”http://host/XWalkRuntimeLib.apk” />.
2 - If we put all the ABIs in the manifest, it is easier on the
servers side, there does not have to be code serving the right apk,
e.g.
<meta-data android:name=”org.xwalk.runtime.x86”
android:value=”http://host/XWalkRuntimeLib.x86.apk” />.
<meta-data android:name=”org.xwalk.runtime.armeabi-v7”
android:value=”http://host/XWalkRuntimeLib.armeabi-v7.apk” />
<meta-data android:name=”org.xwalk.runtime.x86_64”
android:value=”http://host/XWalkRuntimeLib.x86_64.apk” />.
etc ...
Then the app can pick and download the one matching the device ABI.
Otherwise, LGTM.
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
