Ports 搜索

The Ruby CookieJar is a library to help manage client-side cookies in pure Ruby. It enables parsing and setting of cookie headers, alternating between multiple 'jars' of cookies at one time (such as having a set of cookies for each browser or thread), and supports persistence of the cookies in a JSON string. Both Netscape/RFC 2109 cookies and RFC 2965 cookies are supported.

Wt (pronounced as witty) is a C++ library for developing web applications. The API is widget-centric and uses well-tested patterns of desktop GUI development tailored to the web. To the developer, it offers abstraction of many web-specific implementation details, including client-server protocols (HTTP, Ajax, WebSockets), and frees the developer from tedious JavaScript manipulations of HTML and dealing with cross-browser issues. Instead, with Wt, you can focus on actual functionality with a rich set of feature-complete widgets. Unlike old-school page-based frameworks or current-day single-page JavaScript "frameworks", Wt allows you to create stateful applications that are at the same time highly interactive (using WebSockets and Ajax for everything) but still support plain HTML browsers or web crawlers using automatic graceful degradation or progressive enhancement. Things that are natural and simple with Wt would require an impractical amount of development effort otherwise: switching widgets using animations, while retaining clean URLs and browser navigation functions, or having a persistent chat widget open throughout the entire application, that even works in legacy browsers like Microsoft Internet Explorer 6. The library comes with an application server that acts as a stand-alone Http(s)/WebSocket server or integrates through FastCGI with other web servers.

The module can be used to republish a DAAP share. You'll probably want to use Net::DAV::Server or POE::Component::Server::FTP to re-export it in a browseable form.

POE::Component::Client::POP3 is a POE component for interacting with a POP3 server. This means it is an event driven way to communicate with a server that implements Post Office Protocol Version 3 see rfc 1939 for details on the protocol.

POE::Component::Server::TCP implements the SMTP protocol for the server. To support any command other than HELO and QUIT, you'll have to implement it yourself, and define it in your InlineStates, PackageStates, or ObjectStates.

With xfce4-dict you can query a dictionary server (see RFC 2229) to search for the translation or explanation of a word. You can also choose a dictionary offered by the server to improve your search results.

Frontier::RPC implements UserLand Software's XML RPC (Remote Procedure Calls using Extensible Markup Language). Frontier::RPC includes both a client module for making requests to a server and a daemon module for implementing servers. Frontier::RPC uses RPC2 format messages. RPC client connections are made by creating instances of Frontier::Client objects that record the server name, and then issuing `call' requests that send a method name and parameters to the server. RPC daemons are mini-HTTP servers (using HTTP::Daemon from the `libwww' Perl module). Daemons are created by first defining the procedures you want to make available to RPC and then passing a list of those procedures as you create the Frontier::Daemon object. The Frontier::RPC2 module implements the encoding and decoding of XML RPC requests using the XML::Parser Perl module.

Tile38 is an open source (MIT licensed), in-memory geolocation data store, spatial index, and realtime geofence. It supports a variety of object types including lat/lon points, bounding boxes, XYZ tiles, Geohashes, and GeoJSON. Features: Spatial index with search methods such as NEARBY, WITHIN, and INTERSECTS. Realtime geofencing through persistent sockets or webhooks. Object types of lat/lon, bbox, Geohash, GeoJSON, QuadKey, and XYZ tile. Support for lots of Clients Libraries written in many different languages. Variety of client protocols, including http (curl), websockets, telnet, and the Redis RESP. Server responses are RESP or JSON. Full command line interface. Leader / follower replication. In-memory database that persists on disk.

The dnscrypt-proxy provides local service, which can be used directly as your local resolver or as a DNS forwarder, encrypting and authenticating requests using the DNSCrypt [1] protocol and passing them to an upstream server. The DNSCrypt protocol uses high-speed high-security elliptic-curve cryptography and is very similar to DNSCurve [2], but focuses on securing communications between a client and its first-level resolver. While not providing end-to-end security, it protects the local network, which is often the weakest point of the chain, against man-in-the-middle attacks. It also provides some confidentiality to DNS queries. Reference links: 1. https://www.opendns.com/technology/dnscrypt/ 2. http://dnscurve.org

UPnP media server MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices. MediaTomb implements the UPnP MediaServer V 1.0 specification that can be found on http://www.upnp.org/. The current implementation focuses on parts that are required by the specification, however we look into extending the functionality to cover the optional parts of the spec as well.