incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon MacDonald <simon.macdon...@gmail.com>
Subject Re: File API error inconsistency
Date Fri, 24 Feb 2012 15:42:18 GMT
Yeah, I saw that change too. I was wondering what the advantage of
returning an integer vs returning a FileError object?

Simon Mac Donald
http://hi.im/simonmacdonald


On Fri, Feb 24, 2012 at 9:54 AM, Drew Walters <deedubbu@gmail.com> wrote:

> I've been working through the File API mobile-spec failures on
> BlackBerry and have encountered some inconsistency in how error codes
> in the JS are handled.  Some of the JS API
> (DirectoryEntry.removeRecursively, DirectoryReader.readEntries,
> Entry,getMetadata, Entry.getParent, window.requestFileSystem) expect
> the native side to return a FileError object in the error result,
> while the rest expect the native side to just return an integer error
> code (which is used on JS side to create FileError object).
>
> Should the native code return a FileError object or just the integer
> error code?  We need to choose one because it is too error
> prone/frustrating right now to try to get the native side to properly
> handle the error for each individual API.
>

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