android - Crosswalk storage limits -
what storage limits when using crosswalk? same rules as chrome apply, in isolation of app using crosswalk? or in worst case shared global storage limits regular chrome install?
also, crosswalk move data sd card in case core memory fills up, e.g. app uses 1gb of web database?
been looking can't find documentation.
sharing knowledge thoughts on matter - crosswalk (cw) runtime helps full potential of html5, because supports more , advanced html5 features android's default webview, , helps have consistent ui in android apps, irrespective of handset manufacturer.
for that, app contact or work through cw api , interact chrome runtime ensure there consistency , ever gaps present filled cw.
as can see in below architecture diagram, still talks chrome runtime, wouldn't change runtime rules apart ui based rule or apis etc., , at-least not change storage rule or underlying mechanism.
there issues related local storage access cw, issues related api, so per me can expect same storage mechanism, limits , rules cw.
hope helps!

Comments
Post a Comment