react-native/Libraries/WebSocket/RCTWebSocketExecutor.h

/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 */

#import "RCTDefines.h"

#if RCT_DEV // Debug executors are only supported in dev mode

#import "RCTJavaScriptExecutor.h"

@interface RCTWebSocketExecutor : NSObject <RCTJavaScriptExecutor>

- (instancetype)initWithURL:(NSURL *)URL;

@end

#endif
[ReactNative] Expanded license on obj-c files 2015-03-23 13:28:42 -07:00			`/**`
			`* Copyright (c) 2015-present, Facebook, Inc.`
			`* All rights reserved.`
			`*`
			`* This source code is licensed under the BSD-style license found in the`
			`* LICENSE file in the root directory of this source tree. An additional grant`
			`* of patent rights can be found in the PATENTS file in the same directory.`
			`*/`
[ReactNative][RFC] Bring Chrome debugger to OSS. Part 1 2015-03-19 09:55:40 -07:00
Removed debug code from release builds 2015-04-21 09:48:29 -07:00			`#import "RCTDefines.h"`

			`#if RCT_DEV // Debug executors are only supported in dev mode`

[ReactNative][RFC] Bring Chrome debugger to OSS. Part 1 2015-03-19 09:55:40 -07:00			`#import "RCTJavaScriptExecutor.h"`

			`@interface RCTWebSocketExecutor : NSObject <RCTJavaScriptExecutor>`

Refactored module access to allow for lazy loading Summary: public The `bridge.modules` dictionary provides access to all native modules, but this API requires that every module is initialized in advance so that any module can be accessed. This diff introduces a better API that will allow modules to be initialized lazily as they are needed, and deprecates `bridge.modules` (modules that use it will still work, but should be rewritten to use `bridge.moduleClasses` or `-[bridge moduleForName/Class:` instead. The rules are now as follows: * Any module that overrides `init` or `setBridge:` will be initialized on the main thread when the bridge is created * Any module that implements `constantsToExport:` will be initialized later when the config is exported (the module itself will be initialized on a background queue, but `constantsToExport:` will still be called on the main thread. * All other modules will be initialized lazily when a method is first called on them. These rules may seem slightly arcane, but they have the advantage of not violating any assumptions that may have been made by existing code - any module written under the original assumption that it would be initialized synchronously on the main thread when the bridge is created should still function exactly the same, but modules that avoid overriding `init` or `setBridge:` will now be loaded lazily. I've rewritten most of the standard modules to take advantage of this new lazy loading, with the following results: Out of the 65 modules included in UIExplorer: * 16 are initialized on the main thread when the bridge is created * A further 8 are initialized when the config is exported to JS * The remaining 41 will be initialized lazily on-demand Reviewed By: jspahrsummers Differential Revision: D2677695 fb-gh-sync-id: 507ae7e9fd6b563e89292c7371767c978e928f33 2015-11-25 03:09:00 -08:00			`- (instancetype)initWithURL:(NSURL *)URL;`
[ReactNative][RFC] Bring Chrome debugger to OSS. Part 1 2015-03-19 09:55:40 -07:00
			`@end`
Removed debug code from release builds 2015-04-21 09:48:29 -07:00
			`#endif`