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:41:24 GMT
The Connection global houses the constants which you would normally use to
compare the value of to, as per the docs

Connection.WIFI, etc.

Both are required, and both should be common to all platforms.

For iOS, we'll have to move the connection information into a proper
plugin (if its not already there) instead of just dumping it on the
device.connection global.

On 12-02-23 9:32 AM, "Drew Walters" <> wrote:

>There is still a Connection object defined in Connection.js which is
>made globally available during bootstrap (common.js objects).  The end
>user access the network functionality through
> as defined by the spec.
> is globally mapped to the
>NetworkConnection module by bootstrap (common.js objects) as well.
>On Thu, Feb 23, 2012 at 10:20 AM, Becky Gibson <>
>> So, I've started working through the unified JS changs for iOS.   I'm
>> quite sure how to handle the many differences at startup.   If I'm
>> the code right, there seems to be a new NetworkConnection object which
>> replaces the Connection object.   Any reason for renaming this?  It
>> 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
>> 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
>> 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.
>> -becky

View raw message