diff options
Diffstat (limited to 'dev-cpp/wangle/metadata.xml')
| -rw-r--r-- | dev-cpp/wangle/metadata.xml | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/dev-cpp/wangle/metadata.xml b/dev-cpp/wangle/metadata.xml new file mode 100644 index 000000000000..5b7146169a27 --- /dev/null +++ b/dev-cpp/wangle/metadata.xml @@ -0,0 +1,46 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM 'http://www.gentoo.org/dtd/metadata.dtd'> +<pkgmetadata> + <maintainer type="person"> + <description>co-maintainers welcome</description> + <email>lssndrbarbieri@gmail.com</email> + <name>Alessandro Barbieri</name> + </maintainer> + <longdescription lang="en"> +Client / Server abstraction + +You're probably familiar with Java's Netty, or Python's twisted, or similar libraries. + +It is built on top of folly/async/io, so it's one level up the stack from that (or similar abstractions like boost::asio) + +ServerBootstrap - easily manage creation of threadpools and pipelines + +ClientBootstrap - the same for clients + +Pipeline - set up a series of handlers that modify your socket data + +Request / Response abstraction + +This is roughly equivalent to the Finagle library. + +Aims to provide easy testing, load balancing, client pooling, retry logic, etc. for any request/response type service - i.e. thrift, http, etc. + +Service - a matched interface between client/server. A server will implement this interface, and a client will call in to it. These are protocol-specific + +ServiceFilter - a generic filter on a service. Examples: stats, request timeouts, rate limiting + +ServiceFactory - A factory that creates client connections. Any protocol specific setup code goes here + +ServiceFactoryFilter - Generic filters that control how connections are created. Client examples: load balancing, pooling, idle timeouts, markdowns, etc. + +ServerBootstrap + +Easily create a new server + +ServerBootstrap does the work to set up one or multiple acceptor threads, and one or multiple sets of IO threads. The thread pools can be the same. SO_REUSEPORT is automatically supported for multiple accept threads. tcp is most common, although udp is also supported. + </longdescription> + <upstream> + <bugs-to>https://github.com/facebook/wangle/issues</bugs-to> + <remote-id type="github">facebook/wangle</remote-id> + </upstream> +</pkgmetadata> |