incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryce Curtis <>
Subject Re: [post-1.5][Android] Alternatives to file:///android_asset/
Date Thu, 01 Mar 2012 03:51:44 GMT
This would be worth investigating.  Some questions come to mind like
whether this solves the WebSQL problem, can resources be loaded using a
simple url (ie images, audio, video, etc), does this bring in the cross
domain problem, and can this be consistent across all platforms?

On Wed, Feb 29, 2012 at 5:48 PM, Joe Bowser <> wrote:

> Hey
> This release has been rather painful, and I know that this isn't exactly
> the best time, but after looking at WebSQL and the history/iframe issues,
> I'm wondering if we're better off running a local web server or using a
> content provider to serve documents instead of relying on the method we
> have now with file:///android_asset/.  I know that we've talked about it
> before, but given that we're now writing work-around for things that used
> to work, I'm wondering if this might be a better approach.
> I'm just throwing it out there, I have no idea if there are better methods
> than this so far.  Also, we should have this discussion after we release
> 1.5.
> Joe

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message