appium-mac2-driver 4.2.0 → 4.3.1

package/WebDriverAgentMac/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPLogging.h

@@ -1,122 +0,0 @@
-/**
- * In order to provide fast and flexible logging, this project uses Cocoa Lumberjack.
- * 
- * The Google Code page has a wealth of documentation if you have any questions.
- * https://github.com/robbiehanson/CocoaLumberjack
- * 
- * Here's what you need to know concerning how logging is setup for CocoaHTTPServer:
- * 
- * There are 4 log levels:
- * - Error
- * - Warning
- * - Info
- * - Verbose
- * 
- * In addition to this, there is a Trace flag that can be enabled.
- * When tracing is enabled, it spits out the methods that are being called.
- * 
- * Please note that tracing is separate from the log levels.
- * For example, one could set the log level to warning, and enable tracing.
- * 
- * All logging is asynchronous, except errors.
- * To use logging within your own custom files, follow the steps below.
- * 
- * Step 1:
- * Import this header in your implementation file:
- * 
- * #import "HTTPLogging.h"
- * 
- * Step 2:
- * Define your logging level in your implementation file:
- * 
- * // Log levels: off, error, warn, info, verbose
- * static const int httpLogLevel = HTTP_LOG_LEVEL_VERBOSE;
- * 
- * If you wish to enable tracing, you could do something like this:
- * 
- * // Debug levels: off, error, warn, info, verbose
- * static const int httpLogLevel = HTTP_LOG_LEVEL_INFO | HTTP_LOG_FLAG_TRACE;
- * 
- * Step 3:
- * Replace your NSLog statements with HTTPLog statements according to the severity of the message.
- * 
- * NSLog(@"Fatal error, no dohickey found!"); -> HTTPLogError(@"Fatal error, no dohickey found!");
- * 
- * HTTPLog works exactly the same as NSLog.
- * This means you can pass it multiple variables just like NSLog.
- **/
-
-// Define logging context for every log message coming from the HTTP server.
-// The logging context can be extracted from the DDLogMessage from within the logging framework,
-// which gives loggers, formatters, and filters the ability to optionally process them differently.
-
-#define HTTP_LOG_CONTEXT 80
-
-// Configure log levels.
-
-#define HTTP_LOG_FLAG_ERROR   (1 << 0) // 0...00001
-#define HTTP_LOG_FLAG_WARN    (1 << 1) // 0...00010
-#define HTTP_LOG_FLAG_INFO    (1 << 2) // 0...00100
-#define HTTP_LOG_FLAG_VERBOSE (1 << 3) // 0...01000
-
-#define HTTP_LOG_LEVEL_OFF     0                                              // 0...00000
-#define HTTP_LOG_LEVEL_ERROR   (HTTP_LOG_LEVEL_OFF   | HTTP_LOG_FLAG_ERROR)   // 0...00001
-#define HTTP_LOG_LEVEL_WARN    (HTTP_LOG_LEVEL_ERROR | HTTP_LOG_FLAG_WARN)    // 0...00011
-#define HTTP_LOG_LEVEL_INFO    (HTTP_LOG_LEVEL_WARN  | HTTP_LOG_FLAG_INFO)    // 0...00111
-#define HTTP_LOG_LEVEL_VERBOSE (HTTP_LOG_LEVEL_INFO  | HTTP_LOG_FLAG_VERBOSE) // 0...01111
-
-// Setup fine grained logging.
-// The first 4 bits are being used by the standard log levels (0 - 3)
-// 
-// We're going to add tracing, but NOT as a log level.
-// Tracing can be turned on and off independently of log level.
-
-#define HTTP_LOG_FLAG_TRACE   (1 << 4) // 0...10000
-
-// Setup the usual boolean macros.
-
-#define HTTP_LOG_ERROR   (httpLogLevel & HTTP_LOG_FLAG_ERROR)
-#define HTTP_LOG_WARN    (httpLogLevel & HTTP_LOG_FLAG_WARN)
-#define HTTP_LOG_INFO    (httpLogLevel & HTTP_LOG_FLAG_INFO)
-#define HTTP_LOG_VERBOSE (httpLogLevel & HTTP_LOG_FLAG_VERBOSE)
-#define HTTP_LOG_TRACE   (httpLogLevel & HTTP_LOG_FLAG_TRACE)
-
-// Configure asynchronous logging.
-// We follow the default configuration,
-// but we reserve a special macro to easily disable asynchronous logging for debugging purposes.
-
-#define HTTP_LOG_ASYNC_ENABLED   YES
-
-#define HTTP_LOG_ASYNC_ERROR   ( NO && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_WARN    (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_INFO    (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_VERBOSE (YES && HTTP_LOG_ASYNC_ENABLED)
-#define HTTP_LOG_ASYNC_TRACE   (YES && HTTP_LOG_ASYNC_ENABLED)
-
-// Define logging primitives.
-
-#define HTTPLogError(...) { }
-
-#define HTTPLogWarn(...) { }
-
-#define HTTPLogInfo(...) { }
-
-#define HTTPLogVerbose(...) { }
-
-#define HTTPLogTrace() { }
-
-#define HTTPLogTrace2(...) { }
-
-
-#define HTTPLogCError(...) { }
-
-#define HTTPLogCWarn(...) { }
-
-#define HTTPLogCInfo(...) { }
-
-#define HTTPLogCVerbose(...) { }
-
-#define HTTPLogCTrace() { }
-
-#define HTTPLogCTrace2(...) { }
-

package/WebDriverAgentMac/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPMessage.h

@@ -1,48 +0,0 @@
-/**
- * The HTTPMessage class is a simple Objective-C wrapper around Apple's CFHTTPMessage class.
- **/
-
-#import <Foundation/Foundation.h>
-
-#if TARGET_OS_IPHONE
-// Note: You may need to add the CFNetwork Framework to your project
-#import <CFNetwork/CFNetwork.h>
-#endif
-
-#define HTTPVersion1_0  ((NSString *)kCFHTTPVersion1_0)
-#define HTTPVersion1_1  ((NSString *)kCFHTTPVersion1_1)
-
-
-@interface HTTPMessage : NSObject
-{
-  CFHTTPMessageRef message;
-}
-
-- (id)initEmptyRequest;
-
-- (id)initRequestWithMethod:(NSString *)method URL:(NSURL *)url version:(NSString *)version;
-
-- (id)initResponseWithStatusCode:(NSInteger)code description:(NSString *)description version:(NSString *)version;
-
-- (BOOL)appendData:(NSData *)data;
-
-- (BOOL)isHeaderComplete;
-
-- (NSString *)version;
-
-- (NSString *)method;
-- (NSURL *)url;
-
-- (NSInteger)statusCode;
-
-- (NSDictionary *)allHeaderFields;
-- (NSString *)headerField:(NSString *)headerField;
-
-- (void)setHeaderField:(NSString *)headerField value:(NSString *)headerFieldValue;
-
-- (NSData *)messageData;
-
-- (NSData *)body;
-- (void)setBody:(NSData *)body;
-
-@end

package/WebDriverAgentMac/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPMessage.m

@@ -1,114 +0,0 @@
-#import "HTTPMessage.h"
-
-#if ! __has_feature(objc_arc)
-#warning This file must be compiled with ARC. Use -fobjc-arc flag (or convert project to ARC).
-#endif
-
-#pragma clang diagnostic ignored "-Wdirect-ivar-access"
-
-@implementation HTTPMessage
-
-- (id)initEmptyRequest
-{
-  if ((self = [super init]))
-  {
-    message = CFHTTPMessageCreateEmpty(NULL, YES);
-  }
-  return self;
-}
-
-- (id)initRequestWithMethod:(NSString *)method URL:(NSURL *)url version:(NSString *)version
-{
-  if ((self = [super init]))
-  {
-    message = CFHTTPMessageCreateRequest(NULL,
-                                         (__bridge CFStringRef)method,
-                                         (__bridge CFURLRef)url,
-                                         (__bridge CFStringRef)version);
-  }
-  return self;
-}
-
-- (id)initResponseWithStatusCode:(NSInteger)code description:(NSString *)description version:(NSString *)version
-{
-  if ((self = [super init]))
-  {
-    message = CFHTTPMessageCreateResponse(NULL,
-                                          (CFIndex)code,
-                                          (__bridge CFStringRef)description,
-                                          (__bridge CFStringRef)version);
-  }
-  return self;
-}
-
-- (void)dealloc
-{
-  if (message)
-  {
-    CFRelease(message);
-  }
-}
-
-- (BOOL)appendData:(NSData *)data
-{
-  return CFHTTPMessageAppendBytes(message, [data bytes], [data length]);
-}
-
-- (BOOL)isHeaderComplete
-{
-  return CFHTTPMessageIsHeaderComplete(message);
-}
-
-- (NSString *)version
-{
-  return (__bridge_transfer NSString *)CFHTTPMessageCopyVersion(message);
-}
-
-- (NSString *)method
-{
-  return (__bridge_transfer NSString *)CFHTTPMessageCopyRequestMethod(message);
-}
-
-- (NSURL *)url
-{
-  return (__bridge_transfer NSURL *)CFHTTPMessageCopyRequestURL(message);
-}
-
-- (NSInteger)statusCode
-{
-  return (NSInteger)CFHTTPMessageGetResponseStatusCode(message);
-}
-
-- (NSDictionary *)allHeaderFields
-{
-  return (__bridge_transfer NSDictionary *)CFHTTPMessageCopyAllHeaderFields(message);
-}
-
-- (NSString *)headerField:(NSString *)headerField
-{
-  return (__bridge_transfer NSString *)CFHTTPMessageCopyHeaderFieldValue(message, (__bridge CFStringRef)headerField);
-}
-
-- (void)setHeaderField:(NSString *)headerField value:(NSString *)headerFieldValue
-{
-  CFHTTPMessageSetHeaderFieldValue(message,
-                                   (__bridge CFStringRef)headerField,
-                                   (__bridge CFStringRef)headerFieldValue);
-}
-
-- (NSData *)messageData
-{
-  return (__bridge_transfer NSData *)CFHTTPMessageCopySerializedMessage(message);
-}
-
-- (NSData *)body
-{
-  return (__bridge_transfer NSData *)CFHTTPMessageCopyBody(message);
-}
-
-- (void)setBody:(NSData *)body
-{
-  CFHTTPMessageSetBody(message, (__bridge CFDataRef)body);
-}
-
-@end

package/WebDriverAgentMac/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPResponse.h

@@ -1,149 +0,0 @@
-#import <Foundation/Foundation.h>
-
-
-@protocol HTTPResponse
-
-/**
- * Returns the length of the data in bytes.
- * If you don't know the length in advance, implement the isChunked method and have it return YES.
- **/
-- (UInt64)contentLength;
-
-/**
- * The HTTP server supports range requests in order to allow things like
- * file download resumption and optimized streaming on mobile devices.
- **/
-- (UInt64)offset;
-- (void)setOffset:(UInt64)offset;
-
-/**
- * Returns the data for the response.
- * You do not have to return data of the exact length that is given.
- * You may optionally return data of a lesser length.
- * However, you must never return data of a greater length than requested.
- * Doing so could disrupt proper support for range requests.
- * 
- * To support asynchronous responses, read the discussion at the bottom of this header.
- **/
-- (NSData *)readDataOfLength:(NSUInteger)length;
-
-/**
- * Should only return YES after the HTTPConnection has read all available data.
- * That is, all data for the response has been returned to the HTTPConnection via the readDataOfLength method.
- **/
-- (BOOL)isDone;
-
-@optional
-
-/**
- * If you need time to calculate any part of the HTTP response headers (status code or header fields),
- * this method allows you to delay sending the headers so that you may asynchronously execute the calculations.
- * Simply implement this method and return YES until you have everything you need concerning the headers.
- * 
- * This method ties into the asynchronous response architecture of the HTTPConnection.
- * You should read the full discussion at the bottom of this header.
- * 
- * If you return YES from this method,
- * the HTTPConnection will wait for you to invoke the responseHasAvailableData method.
- * After you do, the HTTPConnection will again invoke this method to see if the response is ready to send the headers.
- * 
- * You should only delay sending the headers until you have everything you need concerning just the headers.
- * Asynchronously generating the body of the response is not an excuse to delay sending the headers.
- * Instead you should tie into the asynchronous response architecture, and use techniques such as the isChunked method.
- * 
- * Important: You should read the discussion at the bottom of this header.
- **/
-- (BOOL)delayResponseHeaders;
-
-/**
- * Status code for response.
- * Allows for responses such as redirect (301), etc.
- **/
-- (NSInteger)status;
-
-/**
- * If you want to add any extra HTTP headers to the response,
- * simply return them in a dictionary in this method.
- **/
-- (NSDictionary *)httpHeaders;
-
-/**
- * If you don't know the content-length in advance,
- * implement this method in your custom response class and return YES.
- * 
- * Important: You should read the discussion at the bottom of this header.
- **/
-- (BOOL)isChunked;
-
-/**
- * This method is called from the HTTPConnection class when the connection is closed,
- * or when the connection is finished with the response.
- * If your response is asynchronous, you should implement this method so you know not to
- * invoke any methods on the HTTPConnection after this method is called (as the connection may be deallocated).
- **/
-- (void)connectionDidClose;
-
-@end
-
-
-/**
- * Important notice to those implementing custom asynchronous and/or chunked responses:
- * 
- * HTTPConnection supports asynchronous responses.  All you have to do in your custom response class is
- * asynchronously generate the response, and invoke HTTPConnection's responseHasAvailableData method.
- * You don't have to wait until you have all of the response ready to invoke this method.  For example, if you
- * generate the response in incremental chunks, you could call responseHasAvailableData after generating
- * each chunk.  Please see the HTTPAsyncFileResponse class for an example of how to do this.
- * 
- * The normal flow of events for an HTTPConnection while responding to a request is like this:
- *  - Send http resopnse headers
- *  - Get data from response via readDataOfLength method.
- *  - Add data to asyncSocket's write queue.
- *  - Wait for asyncSocket to notify it that the data has been sent.
- *  - Get more data from response via readDataOfLength method.
- *  - ... continue this cycle until the entire response has been sent.
- * 
- * With an asynchronous response, the flow is a little different.
- * 
- * First the HTTPResponse is given the opportunity to postpone sending the HTTP response headers.
- * This allows the response to asynchronously execute any code needed to calculate a part of the header.
- * An example might be the response needs to generate some custom header fields,
- * or perhaps the response needs to look for a resource on network-attached storage.
- * Since the network-attached storage may be slow, the response doesn't know whether to send a 200 or 404 yet.
- * In situations such as this, the HTTPResponse simply implements the delayResponseHeaders method and returns YES.
- * After returning YES from this method, the HTTPConnection will wait until the response invokes its
- * responseHasAvailableData method. After this occurs, the HTTPConnection will again query the delayResponseHeaders
- * method to see if the response is ready to send the headers.
- * This cycle will continue until the delayResponseHeaders method returns NO.
- * 
- * You should only delay sending the response headers until you have everything you need concerning just the headers.
- * Asynchronously generating the body of the response is not an excuse to delay sending the headers.
- * 
- * After the response headers have been sent, the HTTPConnection calls your readDataOfLength method.
- * You may or may not have any available data at this point. If you don't, then simply return nil.
- * You should later invoke HTTPConnection's responseHasAvailableData when you have data to send.
- * 
- * You don't have to keep track of when you return nil in the readDataOfLength method, or how many times you've invoked
- * responseHasAvailableData. Just simply call responseHasAvailableData whenever you've generated new data, and
- * return nil in your readDataOfLength whenever you don't have any available data in the requested range.
- * HTTPConnection will automatically detect when it should be requesting new data and will act appropriately.
- * 
- * It's important that you also keep in mind that the HTTP server supports range requests.
- * The setOffset method is mandatory, and should not be ignored.
- * Make sure you take into account the offset within the readDataOfLength method.
- * You should also be aware that the HTTPConnection automatically sorts any range requests.
- * So if your setOffset method is called with a value of 100, then you can safely release bytes 0-99.
- * 
- * HTTPConnection can also help you keep your memory footprint small.
- * Imagine you're dynamically generating a 10 MB response.  You probably don't want to load all this data into
- * RAM, and sit around waiting for HTTPConnection to slowly send it out over the network.  All you need to do
- * is pay attention to when HTTPConnection requests more data via readDataOfLength.  This is because HTTPConnection
- * will never allow asyncSocket's write queue to get much bigger than READ_CHUNKSIZE bytes.  You should
- * consider how you might be able to take advantage of this fact to generate your asynchronous response on demand,
- * while at the same time keeping your memory footprint small, and your application lightning fast.
- * 
- * If you don't know the content-length in advanced, you should also implement the isChunked method.
- * This means the response will not include a Content-Length header, and will instead use "Transfer-Encoding: chunked".
- * There's a good chance that if your response is asynchronous and dynamic, it's also chunked.
- * If your response is chunked, you don't need to worry about range requests.
- **/

package/WebDriverAgentMac/WebDriverAgentLib/Vendor/CocoaHTTPServer/HTTPServer.h

@@ -1,200 +0,0 @@
-#import <Foundation/Foundation.h>
-
-@class GCDAsyncSocket;
-@class WebSocket;
-
-#if TARGET_OS_IPHONE
-#if __IPHONE_OS_VERSION_MIN_REQUIRED >= 40000 // iPhone 4.0
-#define IMPLEMENTED_PROTOCOLS <NSNetServiceDelegate>
-#else
-#define IMPLEMENTED_PROTOCOLS 
-#endif
-#else
-#if MAC_OS_X_VERSION_MIN_REQUIRED >= 1060 // Mac OS X 10.6
-#define IMPLEMENTED_PROTOCOLS <NSNetServiceDelegate>
-#else
-#define IMPLEMENTED_PROTOCOLS 
-#endif
-#endif
-
-
-@interface HTTPServer : NSObject IMPLEMENTED_PROTOCOLS
-{
-  // Underlying asynchronous TCP/IP socket
-  GCDAsyncSocket *asyncSocket;
-  
-  // Dispatch queues
-  dispatch_queue_t serverQueue;
-  dispatch_queue_t connectionQueue;
-  void *IsOnServerQueueKey;
-  void *IsOnConnectionQueueKey;
-  
-  // HTTP server configuration
-  NSString *documentRoot;
-  Class connectionClass;
-  NSString *interface;
-  UInt16 port;
-  
-  // NSNetService and related variables
-  NSNetService *netService;
-  NSString *domain;
-  NSString *type;
-  NSString *name;
-  NSString *publishedName;
-  NSDictionary *txtRecordDictionary;
-  
-  // Connection management
-  NSMutableArray *connections;
-  NSLock *connectionsLock;
-  
-  BOOL isRunning;
-}
-
-/**
- * Specifies the document root to serve files from.
- * For example, if you set this to "/Users/<your_username>/Sites",
- * then it will serve files out of the local Sites directory (including subdirectories).
- * 
- * The default value is nil.
- * The default server configuration will not serve any files until this is set.
- * 
- * If you change the documentRoot while the server is running,
- * the change will affect future incoming http connections.
- **/
-- (NSString *)documentRoot;
-- (void)setDocumentRoot:(NSString *)value;
-
-/**
- * The connection class is the class used to handle incoming HTTP connections.
- * 
- * The default value is [HTTPConnection class].
- * You can override HTTPConnection, and then set this to [MyHTTPConnection class].
- * 
- * If you change the connectionClass while the server is running,
- * the change will affect future incoming http connections.
- **/
-- (Class)connectionClass;
-- (void)setConnectionClass:(Class)value;
-
-/**
- * Set what interface you'd like the server to listen on.
- * By default this is nil, which causes the server to listen on all available interfaces like en1, wifi etc.
- * 
- * The interface may be specified by name (e.g. "en1" or "lo0") or by IP address (e.g. "192.168.4.34").
- * You may also use the special strings "localhost" or "loopback" to specify that
- * the socket only accept connections from the local machine.
- **/
-- (NSString *)interface;
-- (void)setInterface:(NSString *)value;
-
-/**
- * The port number to run the HTTP server on.
- * 
- * The default port number is zero, meaning the server will automatically use any available port.
- * This is the recommended port value, as it avoids possible port conflicts with other applications.
- * Technologies such as Bonjour can be used to allow other applications to automatically discover the port number.
- * 
- * Note: As is common on most OS's, you need root privledges to bind to port numbers below 1024.
- * 
- * You can change the port property while the server is running, but it won't affect the running server.
- * To actually change the port the server is listening for connections on you'll need to restart the server.
- * 
- * The listeningPort method will always return the port number the running server is listening for connections on.
- * If the server is not running this method returns 0.
- **/
-- (UInt16)port;
-- (UInt16)listeningPort;
-- (void)setPort:(UInt16)value;
-
-/**
- * Bonjour domain for publishing the service.
- * The default value is "local.".
- * 
- * Note: Bonjour publishing requires you set a type.
- * 
- * If you change the domain property after the bonjour service has already been published (server already started),
- * you'll need to invoke the republishBonjour method to update the broadcasted bonjour service.
- **/
-- (NSString *)domain;
-- (void)setDomain:(NSString *)value;
-
-/**
- * Bonjour name for publishing the service.
- * The default value is "".
- * 
- * If using an empty string ("") for the service name when registering,
- * the system will automatically use the "Computer Name".
- * Using an empty string will also handle name conflicts
- * by automatically appending a digit to the end of the name.
- * 
- * Note: Bonjour publishing requires you set a type.
- * 
- * If you change the name after the bonjour service has already been published (server already started),
- * you'll need to invoke the republishBonjour method to update the broadcasted bonjour service.
- * 
- * The publishedName method will always return the actual name that was published via the bonjour service.
- * If the service is not running this method returns nil.
- **/
-- (NSString *)name;
-- (NSString *)publishedName;
-- (void)setName:(NSString *)value;
-
-/**
- * Bonjour type for publishing the service.
- * The default value is nil.
- * The service will not be published via bonjour unless the type is set.
- * 
- * If you wish to publish the service as a traditional HTTP server, you should set the type to be "_http._tcp.".
- * 
- * If you change the type after the bonjour service has already been published (server already started),
- * you'll need to invoke the republishBonjour method to update the broadcasted bonjour service.
- **/
-- (NSString *)type;
-- (void)setType:(NSString *)value;
-
-/**
- * Republishes the service via bonjour if the server is running.
- * If the service was not previously published, this method will publish it (if the server is running).
- **/
-- (void)republishBonjour;
-
-/**
- * 
- **/
-- (NSDictionary *)TXTRecordDictionary;
-- (void)setTXTRecordDictionary:(NSDictionary *)dict;
-
-/**
- * Attempts to starts the server on the configured port, interface, etc.
- * 
- * If an error occurs, this method returns NO and sets the errPtr (if given).
- * Otherwise returns YES on success.
- * 
- * Some examples of errors that might occur:
- * - You specified the server listen on a port which is already in use by another application.
- * - You specified the server listen on a port number below 1024, which requires root priviledges.
- * 
- * Code Example:
- * 
- * NSError *err = nil;
- * if (![httpServer start:&err])
- * {
- *     NSLog(@"Error starting http server: %@", err);
- * }
- **/
-- (BOOL)start:(NSError **)errPtr;
-
-/**
- * Stops the server, preventing it from accepting any new connections.
- * You may specify whether or not you want to close the existing client connections.
- * 
- * The default stop method (with no arguments) will close any existing connections. (It invokes [self stop:NO])
- **/
-- (void)stop;
-- (void)stop:(BOOL)keepExistingConnections;
-
-- (BOOL)isRunning;
-
-- (NSUInteger)numberOfHTTPConnections;
-
-@end