4 projects tagged "Networking"
Updated 16 Jan 2012
Pagekite.py
| Pop | 118.43 |
|---|---|
| Vit | 6.19 |
Pagekite is software to make servers on "localhost" visible to the wider Internet. It can be used by Web developers to show off their works in progress to clients or colleagues, embedded developers who need direct access to devices in the field, or as an alternative to dynamic DNS for individuals/hobbyists who would rather host their own content than rely on 3rd party hosting. It creates and maintains a tunnel between your server on localhost and a remote "front-end" (a reverse proxy). Only the front-end has to have a visible IP address; the server itself can reside on a heavily firewalled computer, a mobile device, or even an anonymous node on the Tor network.
Updated 17 Feb 2010
htrosbif
| Pop | 34.86 |
|---|---|
| Vit | 1.47 |
htrosbif is a tool that actively probes an HTTP server. It prods the Web server in all sorts of old, new, basic, fancy, spec-compliant, and spec-breaking ways. It tries to characterize both the well-spoken educated responses and the seriously deviant babble it receives in return. Signatures contain no user data, only header names and HTTP-level quirks. As a useful side effect, this might detect reverse proxies, HTTP load balancers, intrusion prevention systems, and Web application firewalls.
Updated 21 Aug 2012
liblacewing
| Pop | 45.65 |
|---|---|
| Vit | 1.57 |
liblacewing is a cross-platform, high-level networking library. It aims to provide a set of straightforward classes for socket communication in C/C++, with a focus on scalability and platform specific optimisations (eg. support for IOCP, epoll, and kqueue).
Updated 12 Mar 2013
spdylay
| Pop | 122.71 |
|---|---|
| Vit | 7.41 |
spdylay is an experimental implementation of Google's SPDY protocol in C. It provides a SPDY framing layer implementation. It does not perform any I/O operations. When the library needs them, it calls the callback functions provided by the application. It also does not include any event polling mechanism, so the application can freely choose the way of handling events. This library code does not depend on any particular SSL library (except for example programs that depend on OpenSSL 1.0.1 or later).
