Ports Search

FunkLoad is a functional and load web tester, written in Python, whose main use cases are: * Functional testing of web projects, and thus regression testing as well. * Performance testing: by loading the web application and monitoring your servers it helps you to pinpoint bottlenecks, giving a detailed report of performance measurement. * Load testing tool to expose bugs that do not surface in cursory testing, like volume testing or longevity testing. * Stress testing tool to overwhelm the web application resources and test the application recoverability. * Writing web agents by scripting any web repetitive task, like checking if a site is alive.

Tidy is a console application. It corrects and cleans up HTML and XML documents by fixing markup errors and upgrading legacy code to modern standards. TidyLib is a C static or dynamic library that developers can integrate into their applications in order to bring all of Tidy's power to your favorite tools. TidyLib is used today in desktop applications, web servers, and more. This is yet a development version. When it will become stable, it will supersedes the ports www/tidy-devel and www/tidy-lib.

The wwwoffled program is a simple proxy server with special features for use with dial-up internet links. This means that it is possible to browse web pages and read them without having to remain connected. * Can be configured to use dial-on-demand for pages that are not cached. * Selection of pages to download next time online + Using normal browser to follow links. + Command line interface to select pages for downloading. * Control which pages can be requested when offline. * Provides non-cached access to intranet servers.

Celluloid::IO provides an event-driven IO system for building fast, scalable network applications that integrates directly with the Celluloid actor library, making it easy to combine both threaded and evented concepts. Celluloid::IO is ideal for servers which handle large numbers of mostly-idle connections, such as Websocket servers or chat/messaging systems. Celluloid::IO provides a different class of actor: one that's slightly slower and heavier than standard Celluloid actors, but one which contains a high-performance reactor just like EventMachine or Cool.io. This means Celluloid::IO actors have the power of both Celluloid actors and evented I/O loops. Unlike certain other evented I/O systems which limit you to a single event loop per process, Celluloid::IO lets you make as many actors as you want, system resources permitting. Rather than callbacks, Celluloid::IO exposes a synchronous API built on duck types of Ruby's own IO classes, such as TCPServer and TCPSocket. These classes work identically to their core Ruby counterparts, but in the scope of Celluloid::IO actors provide "evented" performance. Since they're drop-in replacements for the standard classes, there's no need to rewrite every library just to take advantage of Celluloid::IO's event loop and you can freely switch between evented and blocking IO even over the lifetime of a single connection.

NSCA-ng provides a client-server pair which makes the Nagios command file accessible to remote systems. This allows for submitting passive check results, downtimes, and many other commands to Nagios or compatible monitoring solutions. The submitted data is queued by the NSCA-ng server if Nagios goes down. Multiple check results or commands can be submitted in one go, and multiline plugin output is fully supported. NSCA-ng uses TLS encryption and shared-secret authentication with per-client passwords, as well as fine-grained authorization control. This package contains the NSCA-ng server, which is written in C and uses an event-driven architecture. Disk I/O is avoided unless the data cannot be submitted in one go due to its size (on Linux, the threshold is 4kB). In this case, the data is handed over to Nagios via asynchronously written files. NSCA clients cannot talk to NSCA-ng servers (nor vice versa), but NSCA and NSCA-ng servers can happily run side by side.

The Python Dugong module provides an API for communicating with HTTP 1.1 servers. It is an alternative to the standard library's http.client (formerly httplib) module. In contrast to http.client, Dugong: * allows you to send multiple requests right after each other without having to read the responses first. * supports waiting for 100-continue before sending the request body. * raises an exception instead of silently delivering partial data if the connection is closed before all data has been received. * raises one specific exception (ConnectionClosed) if the connection has been closed (while http.client connection may raise any of BrokenPipeError, BadStatusLine, ConnectionAbortedError, ConnectionResetError, IncompleteRead or simply return '' on read) * supports non-blocking, asynchronous operation and is compatible with the asyncio module. * can in most cases distinguish between an unavailable DNS server and an unresolvable hostname. * is not compatible with old HTTP 0.9 or 1.0 servers. All request and response headers are represented as str, but must be encodable in latin1. Request and response body must be bytes-like objects or binary streams.

Newsstar fetches news and posts it to a local server; INN, s-news and sn are supported, and it should be easy to adapt for other servers with some configuration and extra scripts. It's designed for Unix-like systems, and all the development was done on Linux. There are already plenty of other programs to do this, but what makes newsstar special is that it can make multiple simultaneous connections, not only to one server, but to several, supporting up to 10 threads. Before fetching each article it checks that it hasn't already been downloaded by another thread or in a previous session. It can also pipeline article requests to make better use of available bandwidth. I wrote it because a number of ISPs I have used suffer from unreliable newsfeeds. There is an excellent free server made available by news.individual.net, but it can be a bit slow at times, and using external servers uses more bandwidth. Therefore I wanted a program which could fetch whatever articles my ISP has available, but use the foreign server to avoid missing posts or getting them very late, and to do it as fast as possible.

XS-HTTPD is a WWW server that has the following features: - It is pronounced as "access-HTTP-daemon" - It is SMALL (very small in fact: a factor two to three smaller than normal servers on disk and in memory) - It is FAST (because it is so small and does not do unnecessary things) - Uses very little CPU time - Configurable (configuration compiled in to make it small, but largely overridable on the command line) - Runs user CGI binaries under their own user ID - Gets users' pages under their own user ID, allowing them to really have protected pages (using the built-in authentication mechanism) - Does not fork for every connection (has a fixed number of servers), only to replace a lost server (in case of timeouts). - Comes with some other useful programs - Offers Server-Side Includes for many common tasks, including built-in page counters (text or graphical) - Supports PHP and other interpreted file formats - Supports automatic decompression to save diskspace and bandwidth - Serves SSL (https) and http connections through the same daemon - Full support for IPv6

N.A.D.A.R. is a network tank battle game. You can play N.A.D.A.R. with computer players and human players over the network. This port installs "/usr/X11R6/bin/nadars" and "/usr/X11R6/bin/nadar". "nadars" is a server of N.A.D.A.R. Run it before playing N.A.D.A.R. "nadar" is a client of N.A.D.A.R. for X. Run it after nadars starts. Example: server-machine> nadars client-machine1> nadar -s [Server's hostname] -p [Player's name] client-machine2> nadar -s [Server's hostname] -p [Player's name] ... If playing speed is very slow, Run nadar as below with size option. client-machine> nadar -s [Server's hostname] -p [Player's name] -size 30 See nadars(1) and nadar(1) for more details.

This program writes short movies with your Canon DSLR camera directly to the computer. The camera must have Live View feature to work; supported models include Canon EOS 450D, Canon EOS 1000D, Canon 40D, Canon 50D, Canon 5D Mark II, Canon 1Ds Mark III. The program offers preview, Av, Tv, and WB control. While some newer models provide video recording natively, this program can be useful if your camera does not have this option. Video will be recorded using MJPEG codec, with no sound, roughly at 22 FPS (depends on your hardware: camera and computer). Image size is also camera dependent: 848x560 for 450D; 1024x680 for 40D, 50D, and top models; 768x512 for 1000D. Resulting file is simply a collection of Live View frames stored sequentially without any compression in AVI container (expect file size to be quite large).