incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: Unified JS and iOS
Date Thu, 23 Feb 2012 17:29:42 GMT
I believe the methods you point out are simply convenience methods.

The Connection object is based on this spec:

... Which exposes a single "type" property according to the spec. That's
the only thing we *have* to provide (and thus our documentation

That being said there is a new internal draft in the works at the W3C:

So we have more work down the road :)

For the initial cordova-js drop I am working towards just providing what
our docs say we have / passing mobile-spec (minus that little toURI ->
toURL method hiccup that we went over earlier).

Let me get the relevant code branches online for you to peruse and
hopefully it will start to make more sense.

On 12-02-23 8:20 AM, "Becky Gibson" <> wrote:

>So, I've started working through the unified JS changs for iOS.   I'm not
>quite sure how to handle the many differences at startup.   If I'm reading
>the code right, there seems to be a new NetworkConnection object which
>replaces the Connection object.   Any reason for renaming this?  It seems
>to me we should try to make a few api/object name changes as possible to
>make upgrading easier for folks.  Also, since we are not going to get iOS
>updated for 1.5, we will have a discrepancy between platforms with some
>using NetworkConnection and iOS at least still using Connection.
>Is there any requirement fo this NetworkConenction.getInfo() api?  I can
>certainly override that module for iOS to continue with the current iOS
>implementation  or I can implement a getInfo() api.  The same issue occurs
>for the Device object - other platforms implement a getInfo() api to get
>the info.  iOS calls out to JS to set the info during startup.

View raw message