cannam@134: // Copyright (c) 2013-2014 Sandstorm Development Group, Inc. and contributors cannam@134: // Licensed under the MIT License: cannam@134: // cannam@134: // Permission is hereby granted, free of charge, to any person obtaining a copy cannam@134: // of this software and associated documentation files (the "Software"), to deal cannam@134: // in the Software without restriction, including without limitation the rights cannam@134: // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell cannam@134: // copies of the Software, and to permit persons to whom the Software is cannam@134: // furnished to do so, subject to the following conditions: cannam@134: // cannam@134: // The above copyright notice and this permission notice shall be included in cannam@134: // all copies or substantial portions of the Software. cannam@134: // cannam@134: // THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR cannam@134: // IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, cannam@134: // FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE cannam@134: // AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER cannam@134: // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, cannam@134: // OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN cannam@134: // THE SOFTWARE. cannam@134: cannam@134: #ifndef KJ_ASYNC_IO_H_ cannam@134: #define KJ_ASYNC_IO_H_ cannam@134: cannam@134: #if defined(__GNUC__) && !KJ_HEADER_WARNINGS cannam@134: #pragma GCC system_header cannam@134: #endif cannam@134: cannam@134: #include "async.h" cannam@134: #include "function.h" cannam@134: #include "thread.h" cannam@134: #include "time.h" cannam@134: cannam@134: struct sockaddr; cannam@134: cannam@134: namespace kj { cannam@134: cannam@134: class UnixEventPort; cannam@134: class NetworkAddress; cannam@134: cannam@134: // ======================================================================================= cannam@134: // Streaming I/O cannam@134: cannam@134: class AsyncInputStream { cannam@134: // Asynchronous equivalent of InputStream (from io.h). cannam@134: cannam@134: public: cannam@134: virtual Promise read(void* buffer, size_t minBytes, size_t maxBytes) = 0; cannam@134: virtual Promise tryRead(void* buffer, size_t minBytes, size_t maxBytes) = 0; cannam@134: cannam@134: Promise read(void* buffer, size_t bytes); cannam@134: }; cannam@134: cannam@134: class AsyncOutputStream { cannam@134: // Asynchronous equivalent of OutputStream (from io.h). cannam@134: cannam@134: public: cannam@134: virtual Promise write(const void* buffer, size_t size) = 0; cannam@134: virtual Promise write(ArrayPtr> pieces) = 0; cannam@134: }; cannam@134: cannam@134: class AsyncIoStream: public AsyncInputStream, public AsyncOutputStream { cannam@134: // A combination input and output stream. cannam@134: cannam@134: public: cannam@134: virtual void shutdownWrite() = 0; cannam@134: // Cleanly shut down just the write end of the stream, while keeping the read end open. cannam@134: cannam@134: virtual void abortRead() {} cannam@134: // Similar to shutdownWrite, but this will shut down the read end of the stream, and should only cannam@134: // be called when an error has occurred. cannam@134: cannam@134: virtual void getsockopt(int level, int option, void* value, uint* length); cannam@134: virtual void setsockopt(int level, int option, const void* value, uint length); cannam@134: // Corresponds to getsockopt() and setsockopt() syscalls. Will throw an "unimplemented" exception cannam@134: // if the stream is not a socket or the option is not appropriate for the socket type. The cannam@134: // default implementations always throw "unimplemented". cannam@134: cannam@134: virtual void getsockname(struct sockaddr* addr, uint* length); cannam@134: virtual void getpeername(struct sockaddr* addr, uint* length); cannam@134: // Corresponds to getsockname() and getpeername() syscalls. Will throw an "unimplemented" cannam@134: // exception if the stream is not a socket. The default implementations always throw cannam@134: // "unimplemented". cannam@134: // cannam@134: // Note that we don't provide methods that return NetworkAddress because it usually wouldn't cannam@134: // be useful. You can't connect() to or listen() on these addresses, obviously, because they are cannam@134: // ephemeral addresses for a single connection. cannam@134: }; cannam@134: cannam@134: struct OneWayPipe { cannam@134: // A data pipe with an input end and an output end. (Typically backed by pipe() system call.) cannam@134: cannam@134: Own in; cannam@134: Own out; cannam@134: }; cannam@134: cannam@134: struct TwoWayPipe { cannam@134: // A data pipe that supports sending in both directions. Each end's output sends data to the cannam@134: // other end's input. (Typically backed by socketpair() system call.) cannam@134: cannam@134: Own ends[2]; cannam@134: }; cannam@134: cannam@134: class ConnectionReceiver { cannam@134: // Represents a server socket listening on a port. cannam@134: cannam@134: public: cannam@134: virtual Promise> accept() = 0; cannam@134: // Accept the next incoming connection. cannam@134: cannam@134: virtual uint getPort() = 0; cannam@134: // Gets the port number, if applicable (i.e. if listening on IP). This is useful if you didn't cannam@134: // specify a port when constructing the NetworkAddress -- one will have been assigned cannam@134: // automatically. cannam@134: cannam@134: virtual void getsockopt(int level, int option, void* value, uint* length); cannam@134: virtual void setsockopt(int level, int option, const void* value, uint length); cannam@134: // Same as the methods of AsyncIoStream. cannam@134: }; cannam@134: cannam@134: // ======================================================================================= cannam@134: // Datagram I/O cannam@134: cannam@134: class AncillaryMessage { cannam@134: // Represents an ancillary message (aka control message) received using the recvmsg() system cannam@134: // call (or equivalent). Most apps will not use this. cannam@134: cannam@134: public: cannam@134: inline AncillaryMessage(int level, int type, ArrayPtr data); cannam@134: AncillaryMessage() = default; cannam@134: cannam@134: inline int getLevel() const; cannam@134: // Originating protocol / socket level. cannam@134: cannam@134: inline int getType() const; cannam@134: // Protocol-specific message type. cannam@134: cannam@134: template cannam@134: inline Maybe as(); cannam@134: // Interpret the ancillary message as the given struct type. Most ancillary messages are some cannam@134: // sort of struct, so this is a convenient way to access it. Returns nullptr if the message cannam@134: // is smaller than the struct -- this can happen if the message was truncated due to cannam@134: // insufficient ancillary buffer space. cannam@134: cannam@134: template cannam@134: inline ArrayPtr asArray(); cannam@134: // Interpret the ancillary message as an array of items. If the message size does not evenly cannam@134: // divide into elements of type T, the remainder is discarded -- this can happen if the message cannam@134: // was truncated due to insufficient ancillary buffer space. cannam@134: cannam@134: private: cannam@134: int level; cannam@134: int type; cannam@134: ArrayPtr data; cannam@134: // Message data. In most cases you should use `as()` or `asArray()`. cannam@134: }; cannam@134: cannam@134: class DatagramReceiver { cannam@134: // Class encapsulating the recvmsg() system call. You must specify the DatagramReceiver's cannam@134: // capacity in advance; if a received packet is larger than the capacity, it will be truncated. cannam@134: cannam@134: public: cannam@134: virtual Promise receive() = 0; cannam@134: // Receive a new message, overwriting this object's content. cannam@134: // cannam@134: // receive() may reuse the same buffers for content and ancillary data with each call. cannam@134: cannam@134: template cannam@134: struct MaybeTruncated { cannam@134: T value; cannam@134: cannam@134: bool isTruncated; cannam@134: // True if the Receiver's capacity was insufficient to receive the value and therefore the cannam@134: // value is truncated. cannam@134: }; cannam@134: cannam@134: virtual MaybeTruncated> getContent() = 0; cannam@134: // Get the content of the datagram. cannam@134: cannam@134: virtual MaybeTruncated> getAncillary() = 0; cannam@134: // Ancilarry messages received with the datagram. See the recvmsg() system call and the cmsghdr cannam@134: // struct. Most apps don't need this. cannam@134: // cannam@134: // If the returned value is truncated, then the last message in the array may itself be cannam@134: // truncated, meaning its as() method will return nullptr or its asArray() method will cannam@134: // return fewer elements than expected. Truncation can also mean that additional messages were cannam@134: // available but discarded. cannam@134: cannam@134: virtual NetworkAddress& getSource() = 0; cannam@134: // Get the datagram sender's address. cannam@134: cannam@134: struct Capacity { cannam@134: size_t content = 8192; cannam@134: // How much space to allocate for the datagram content. If a datagram is received that is cannam@134: // larger than this, it will be truncated, with no way to recover the tail. cannam@134: cannam@134: size_t ancillary = 0; cannam@134: // How much space to allocate for ancillary messages. As with content, if the ancillary data cannam@134: // is larger than this, it will be truncated. cannam@134: }; cannam@134: }; cannam@134: cannam@134: class DatagramPort { cannam@134: public: cannam@134: virtual Promise send(const void* buffer, size_t size, NetworkAddress& destination) = 0; cannam@134: virtual Promise send(ArrayPtr> pieces, cannam@134: NetworkAddress& destination) = 0; cannam@134: cannam@134: virtual Own makeReceiver( cannam@134: DatagramReceiver::Capacity capacity = DatagramReceiver::Capacity()) = 0; cannam@134: // Create a new `Receiver` that can be used to receive datagrams. `capacity` specifies how much cannam@134: // space to allocate for the received message. The `DatagramPort` must outlive the `Receiver`. cannam@134: cannam@134: virtual uint getPort() = 0; cannam@134: // Gets the port number, if applicable (i.e. if listening on IP). This is useful if you didn't cannam@134: // specify a port when constructing the NetworkAddress -- one will have been assigned cannam@134: // automatically. cannam@134: cannam@134: virtual void getsockopt(int level, int option, void* value, uint* length); cannam@134: virtual void setsockopt(int level, int option, const void* value, uint length); cannam@134: // Same as the methods of AsyncIoStream. cannam@134: }; cannam@134: cannam@134: // ======================================================================================= cannam@134: // Networks cannam@134: cannam@134: class NetworkAddress { cannam@134: // Represents a remote address to which the application can connect. cannam@134: cannam@134: public: cannam@134: virtual Promise> connect() = 0; cannam@134: // Make a new connection to this address. cannam@134: // cannam@134: // The address must not be a wildcard ("*"). If it is an IP address, it must have a port number. cannam@134: cannam@134: virtual Own listen() = 0; cannam@134: // Listen for incoming connections on this address. cannam@134: // cannam@134: // The address must be local. cannam@134: cannam@134: virtual Own bindDatagramPort(); cannam@134: // Open this address as a datagram (e.g. UDP) port. cannam@134: // cannam@134: // The address must be local. cannam@134: cannam@134: virtual Own clone() = 0; cannam@134: // Returns an equivalent copy of this NetworkAddress. cannam@134: cannam@134: virtual String toString() = 0; cannam@134: // Produce a human-readable string which hopefully can be passed to Network::parseAddress() cannam@134: // to reproduce this address, although whether or not that works of course depends on the Network cannam@134: // implementation. This should be called only to display the address to human users, who will cannam@134: // hopefully know what they are able to do with it. cannam@134: }; cannam@134: cannam@134: class Network { cannam@134: // Factory for NetworkAddress instances, representing the network services offered by the cannam@134: // operating system. cannam@134: // cannam@134: // This interface typically represents broad authority, and well-designed code should limit its cannam@134: // use to high-level startup code and user interaction. Low-level APIs should accept cannam@134: // NetworkAddress instances directly and work from there, if at all possible. cannam@134: cannam@134: public: cannam@134: virtual Promise> parseAddress(StringPtr addr, uint portHint = 0) = 0; cannam@134: // Construct a network address from a user-provided string. The format of the address cannam@134: // strings is not specified at the API level, and application code should make no assumptions cannam@134: // about them. These strings should always be provided by humans, and said humans will know cannam@134: // what format to use in their particular context. cannam@134: // cannam@134: // `portHint`, if provided, specifies the "standard" IP port number for the application-level cannam@134: // service in play. If the address turns out to be an IP address (v4 or v6), and it lacks a cannam@134: // port number, this port will be used. If `addr` lacks a port number *and* `portHint` is cannam@134: // omitted, then the returned address will only support listen() and bindDatagramPort() cannam@134: // (not connect()), and an unused port will be chosen each time one of those methods is called. cannam@134: cannam@134: virtual Own getSockaddr(const void* sockaddr, uint len) = 0; cannam@134: // Construct a network address from a legacy struct sockaddr. cannam@134: }; cannam@134: cannam@134: // ======================================================================================= cannam@134: // I/O Provider cannam@134: cannam@134: class AsyncIoProvider { cannam@134: // Class which constructs asynchronous wrappers around the operating system's I/O facilities. cannam@134: // cannam@134: // Generally, the implementation of this interface must integrate closely with a particular cannam@134: // `EventLoop` implementation. Typically, the EventLoop implementation itself will provide cannam@134: // an AsyncIoProvider. cannam@134: cannam@134: public: cannam@134: virtual OneWayPipe newOneWayPipe() = 0; cannam@134: // Creates an input/output stream pair representing the ends of a one-way pipe (e.g. created with cannam@134: // the pipe(2) system call). cannam@134: cannam@134: virtual TwoWayPipe newTwoWayPipe() = 0; cannam@134: // Creates two AsyncIoStreams representing the two ends of a two-way pipe (e.g. created with cannam@134: // socketpair(2) system call). Data written to one end can be read from the other. cannam@134: cannam@134: virtual Network& getNetwork() = 0; cannam@134: // Creates a new `Network` instance representing the networks exposed by the operating system. cannam@134: // cannam@134: // DO NOT CALL THIS except at the highest levels of your code, ideally in the main() function. If cannam@134: // you call this from low-level code, then you are preventing higher-level code from injecting an cannam@134: // alternative implementation. Instead, if your code needs to use network functionality, it cannam@134: // should ask for a `Network` as a constructor or method parameter, so that higher-level code can cannam@134: // chose what implementation to use. The system network is essentially a singleton. See: cannam@134: // http://www.object-oriented-security.org/lets-argue/singletons cannam@134: // cannam@134: // Code that uses the system network should not make any assumptions about what kinds of cannam@134: // addresses it will parse, as this could differ across platforms. String addresses should come cannam@134: // strictly from the user, who will know how to write them correctly for their system. cannam@134: // cannam@134: // With that said, KJ currently supports the following string address formats: cannam@134: // - IPv4: "1.2.3.4", "1.2.3.4:80" cannam@134: // - IPv6: "1234:5678::abcd", "[1234:5678::abcd]:80" cannam@134: // - Local IP wildcard (covers both v4 and v6): "*", "*:80" cannam@134: // - Symbolic names: "example.com", "example.com:80", "example.com:http", "1.2.3.4:http" cannam@134: // - Unix domain: "unix:/path/to/socket" cannam@134: cannam@134: struct PipeThread { cannam@134: // A combination of a thread and a two-way pipe that communicates with that thread. cannam@134: // cannam@134: // The fields are intentionally ordered so that the pipe will be destroyed (and therefore cannam@134: // disconnected) before the thread is destroyed (and therefore joined). Thus if the thread cannam@134: // arranges to exit when it detects disconnect, destruction should be clean. cannam@134: cannam@134: Own thread; cannam@134: Own pipe; cannam@134: }; cannam@134: cannam@134: virtual PipeThread newPipeThread( cannam@134: Function startFunc) = 0; cannam@134: // Create a new thread and set up a two-way pipe (socketpair) which can be used to communicate cannam@134: // with it. One end of the pipe is passed to the thread's start function and the other end of cannam@134: // the pipe is returned. The new thread also gets its own `AsyncIoProvider` instance and will cannam@134: // already have an active `EventLoop` when `startFunc` is called. cannam@134: // cannam@134: // TODO(someday): I'm not entirely comfortable with this interface. It seems to be doing too cannam@134: // much at once but I'm not sure how to cleanly break it down. cannam@134: cannam@134: virtual Timer& getTimer() = 0; cannam@134: // Returns a `Timer` based on real time. Time does not pass while event handlers are running -- cannam@134: // it only updates when the event loop polls for system events. This means that calling `now()` cannam@134: // on this timer does not require a system call. cannam@134: // cannam@134: // This timer is not affected by changes to the system date. It is unspecified whether the timer cannam@134: // continues to count while the system is suspended. cannam@134: }; cannam@134: cannam@134: class LowLevelAsyncIoProvider { cannam@134: // Similar to `AsyncIoProvider`, but represents a lower-level interface that may differ on cannam@134: // different operating systems. You should prefer to use `AsyncIoProvider` over this interface cannam@134: // whenever possible, as `AsyncIoProvider` is portable and friendlier to dependency-injection. cannam@134: // cannam@134: // On Unix, this interface can be used to import native file descriptors into the async framework. cannam@134: // Different implementations of this interface might work on top of different event handling cannam@134: // primitives, such as poll vs. epoll vs. kqueue vs. some higher-level event library. cannam@134: // cannam@134: // On Windows, this interface can be used to import native HANDLEs into the async framework. cannam@134: // Different implementations of this interface might work on top of different event handling cannam@134: // primitives, such as I/O completion ports vs. completion routines. cannam@134: // cannam@134: // TODO(port): Actually implement Windows support. cannam@134: cannam@134: public: cannam@134: // --------------------------------------------------------------------------- cannam@134: // Unix-specific stuff cannam@134: cannam@134: enum Flags { cannam@134: // Flags controlling how to wrap a file descriptor. cannam@134: cannam@134: TAKE_OWNERSHIP = 1 << 0, cannam@134: // The returned object should own the file descriptor, automatically closing it when destroyed. cannam@134: // The close-on-exec flag will be set on the descriptor if it is not already. cannam@134: // cannam@134: // If this flag is not used, then the file descriptor is not automatically closed and the cannam@134: // close-on-exec flag is not modified. cannam@134: cannam@134: ALREADY_CLOEXEC = 1 << 1, cannam@134: // Indicates that the close-on-exec flag is known already to be set, so need not be set again. cannam@134: // Only relevant when combined with TAKE_OWNERSHIP. cannam@134: // cannam@134: // On Linux, all system calls which yield new file descriptors have flags or variants which cannam@134: // set the close-on-exec flag immediately. Unfortunately, other OS's do not. cannam@134: cannam@134: ALREADY_NONBLOCK = 1 << 2 cannam@134: // Indicates that the file descriptor is known already to be in non-blocking mode, so the flag cannam@134: // need not be set again. Otherwise, all wrap*Fd() methods will enable non-blocking mode cannam@134: // automatically. cannam@134: // cannam@134: // On Linux, all system calls which yield new file descriptors have flags or variants which cannam@134: // enable non-blocking mode immediately. Unfortunately, other OS's do not. cannam@134: }; cannam@134: cannam@134: virtual Own wrapInputFd(int fd, uint flags = 0) = 0; cannam@134: // Create an AsyncInputStream wrapping a file descriptor. cannam@134: // cannam@134: // `flags` is a bitwise-OR of the values of the `Flags` enum. cannam@134: cannam@134: virtual Own wrapOutputFd(int fd, uint flags = 0) = 0; cannam@134: // Create an AsyncOutputStream wrapping a file descriptor. cannam@134: // cannam@134: // `flags` is a bitwise-OR of the values of the `Flags` enum. cannam@134: cannam@134: virtual Own wrapSocketFd(int fd, uint flags = 0) = 0; cannam@134: // Create an AsyncIoStream wrapping a socket file descriptor. cannam@134: // cannam@134: // `flags` is a bitwise-OR of the values of the `Flags` enum. cannam@134: cannam@134: virtual Promise> wrapConnectingSocketFd(int fd, uint flags = 0) = 0; cannam@134: // Create an AsyncIoStream wrapping a socket that is in the process of connecting. The returned cannam@134: // promise should not resolve until connection has completed -- traditionally indicated by the cannam@134: // descriptor becoming writable. cannam@134: // cannam@134: // `flags` is a bitwise-OR of the values of the `Flags` enum. cannam@134: cannam@134: virtual Own wrapListenSocketFd(int fd, uint flags = 0) = 0; cannam@134: // Create an AsyncIoStream wrapping a listen socket file descriptor. This socket should already cannam@134: // have had `bind()` and `listen()` called on it, so it's ready for `accept()`. cannam@134: // cannam@134: // `flags` is a bitwise-OR of the values of the `Flags` enum. cannam@134: cannam@134: virtual Own wrapDatagramSocketFd(int fd, uint flags = 0); cannam@134: cannam@134: virtual Timer& getTimer() = 0; cannam@134: // Returns a `Timer` based on real time. Time does not pass while event handlers are running -- cannam@134: // it only updates when the event loop polls for system events. This means that calling `now()` cannam@134: // on this timer does not require a system call. cannam@134: // cannam@134: // This timer is not affected by changes to the system date. It is unspecified whether the timer cannam@134: // continues to count while the system is suspended. cannam@134: }; cannam@134: cannam@134: Own newAsyncIoProvider(LowLevelAsyncIoProvider& lowLevel); cannam@134: // Make a new AsyncIoProvider wrapping a `LowLevelAsyncIoProvider`. cannam@134: cannam@134: struct AsyncIoContext { cannam@134: Own lowLevelProvider; cannam@134: Own provider; cannam@134: WaitScope& waitScope; cannam@134: cannam@134: UnixEventPort& unixEventPort; cannam@134: // TEMPORARY: Direct access to underlying UnixEventPort, mainly for waiting on signals. This cannam@134: // field will go away at some point when we have a chance to improve these interfaces. cannam@134: }; cannam@134: cannam@134: AsyncIoContext setupAsyncIo(); cannam@134: // Convenience method which sets up the current thread with everything it needs to do async I/O. cannam@134: // The returned objects contain an `EventLoop` which is wrapping an appropriate `EventPort` for cannam@134: // doing I/O on the host system, so everything is ready for the thread to start making async calls cannam@134: // and waiting on promises. cannam@134: // cannam@134: // You would typically call this in your main() loop or in the start function of a thread. cannam@134: // Example: cannam@134: // cannam@134: // int main() { cannam@134: // auto ioContext = kj::setupAsyncIo(); cannam@134: // cannam@134: // // Now we can call an async function. cannam@134: // Promise textPromise = getHttp(*ioContext.provider, "http://example.com"); cannam@134: // cannam@134: // // And we can wait for the promise to complete. Note that you can only use `wait()` cannam@134: // // from the top level, not from inside a promise callback. cannam@134: // String text = textPromise.wait(ioContext.waitScope); cannam@134: // print(text); cannam@134: // return 0; cannam@134: // } cannam@134: // cannam@134: // WARNING: An AsyncIoContext can only be used in the thread and process that created it. In cannam@134: // particular, note that after a fork(), an AsyncIoContext created in the parent process will cannam@134: // not work correctly in the child, even if the parent ceases to use its copy. In particular cannam@134: // note that this means that server processes which daemonize themselves at startup must wait cannam@134: // until after daemonization to create an AsyncIoContext. cannam@134: cannam@134: // ======================================================================================= cannam@134: // inline implementation details cannam@134: cannam@134: inline AncillaryMessage::AncillaryMessage( cannam@134: int level, int type, ArrayPtr data) cannam@134: : level(level), type(type), data(data) {} cannam@134: cannam@134: inline int AncillaryMessage::getLevel() const { return level; } cannam@134: inline int AncillaryMessage::getType() const { return type; } cannam@134: cannam@134: template cannam@134: inline Maybe AncillaryMessage::as() { cannam@134: if (data.size() >= sizeof(T)) { cannam@134: return *reinterpret_cast(data.begin()); cannam@134: } else { cannam@134: return nullptr; cannam@134: } cannam@134: } cannam@134: cannam@134: template cannam@134: inline ArrayPtr AncillaryMessage::asArray() { cannam@134: return arrayPtr(reinterpret_cast(data.begin()), data.size() / sizeof(T)); cannam@134: } cannam@134: cannam@134: } // namespace kj cannam@134: cannam@134: #endif // KJ_ASYNC_IO_H_