人行横道的存储限制 [英] Crosswalk storage limits

问题描述

使用Crosswalk时的存储限制是多少？是否只是使用Crosswalk隔离应用程序的与Chrome浏览器相同的规则？还是在最坏的情况下通过常规的Chrome安装共享全球存储限制？

What are the storage limits when using Crosswalk? Do the same rules as for Chrome apply, just in isolation of the app using Crosswalk? Or in the worst case shared global storage limits with the regular Chrome install?

此外，如果核心内存已满，例如，Crosswalk是否会将所有数据移至SD卡。一个应用程序使用了说说1GB的某个Web数据库？

Also, will Crosswalk move any data to the SD card in case the core memory fills up, e.g. an app uses say 1GB of some web database?

曾经看过，但实际上找不到任何文档。

Been looking but really can't find any documentation.

推荐答案

分享我对这件事的认识-CrossWalk（CW）只是一个运行时，可帮助充分发挥HTML5的潜力，因为它支持更多和高级的HTML5功能而不是Android的默认WebView，并且无论谁是手机制造商，都有助于在所有Android应用程序中拥有一致的UI。

Sharing my knowledge thoughts on the matter - CrossWalk (CW) is just a runtime which helps get full potential of HTML5, because it supports more and advanced HTML5 features than Android's default WebView, and it helps to have a consistent UI in all Android apps, irrespective of who is handset manufacturer.

为此，应用程序将与CW API联系或通过其工作，并且它将与Chrome运行时进行交互，以确保一致性并消除存在的空白。

For that, app will contact or work through CW API and it will interact with Chrome runtime to ensure that there is consistency and what ever gaps are present is filled by CW.

如下面的架构图所示，它仍然与Chrome运行时保持联系，因此除了基于UI的规则或API等外，它不会更改任何运行时规则，并且至少不会更改任何存储规则或基础机制。

As we can see in below architecture diagram, it still talks with Chrome runtime, so it wouldn't change any runtime rules apart from UI based rule or APIs etc., and at-least it would not change any storage rule or underlying mechanism.

存在与使用CW进行本地存储访问有关的问题，但这些问题与API有关，因此，按照我的观点，您可以期望CW具有相同的存储机制，限制和规则。

There are issues related to local storage access with CW, but those issues are related to API, so as per me you can expect same storage mechanism, limits and rules with CW.

希望这会有所帮助！

这篇关于人行横道的存储限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！