Ports 搜索

Server runner for testing Groonga full-text search engine.

Httperf is a tool for measuring web server performance. It provides a flexible facility for generating various HTTP workloads and for measuring server performance. The focus of httperf is not on implementing one particular benchmark but on providing a robust, high-performance tool that facilitates the construction of both micro- and macro-level benchmarks. The three distinguishing characteristics of httperf are its robustness, which includes the ability to generate and sustain server overload, support for the HTTP/1.1 and SSL protocols, and its extensibility to new workload generators and performance measurements.

LWP::UserAgent is the default module for issuing HTTP requests from Perl. It has a keep_alive setting which by default allows unlimited requests to the same server. Some servers will disconnect you after a limited number of requests (in Apache 2 this is achieved with the MaxKeepAliveRequests directive). This module allows you to limit the maximum number of keep alive requests to a server.

The Web Service Addressing protocol is used to select certain service and port on a SOAP server, just like the "Host" header in "HTTP". The basic SOAP design uses the URI and the "soapAction" header of HTTP (in case it uses HTTP, by far the most often used transport mechanism) However, when the server is hidden behind firewalls and proxies, these fields are rewritten or replaced. This means that the definitions by the WSDL for the client can differ from the configuration of the

Nagios::Plugin::Beanstalk - Nagios plugin to observe Beanstalkd queue server.

AmphetaDesk is a free, cross platform, open-sourced, syndicated news aggregator - it obediently sits on your desktop, downloads the latest news that interests you, and displays them in a quick and easy to use (and customizable!) webpage. With thousands of channels available, AmphetaDesk can shave hours off your day - and you'll look smart to all your friends! Egotism never had it better!

gdnsd is an Authoritative-only DNS server. The initial g stands for Geographic, as gdnsd offers a plugin system for geographic (or other sorts of) balancing, redirection, and service-state-conscious failover. If you don't care about that feature, it's still quite good at being a very fast, lean, and resilient authoritative-only server for static DNS data. gdnsd is written in C using libev and pthreads with a focus on high performance, low latency service. It does not offer any form of caching or recursive service, and does not support DNSSEC.

gdnsd is an Authoritative-only DNS server. The initial g stands for Geographic, as gdnsd offers a plugin system for geographic (or other sorts of) balancing, redirection, and service-state-conscious failover. If you don't care about that feature, it's still quite good at being a very fast, lean, and resilient authoritative-only server for static DNS data. gdnsd is written in C using libev and pthreads with a focus on high performance, low latency service. It does not offer any form of caching or recursive service, and does not support DNSSEC.

Test::WWW::Mechanize is a subclass of WWW::Mechanize that incorporates features for web application testing. The Test::WWW::Mechanize::Catalyst module meshes the two to allow easy testing of Catalyst applications without needing to starting up a web server. Testing web applications has always been a bit tricky, normally requiring starting a web server for your application and making real HTTP requests to it. This module allows you to test Catalyst web applications but does not require a server or issue HTTP requests. Instead, it passes the HTTP request object directly to Catalyst. Thus you do not need to use a real hostname: "http://localhost/" will do. However, this is optional. The following two lines of code do exactly the same thing:

decoded_content utility method to WWW::Mechanize.