Ports 搜索

Ever tried logging Apache page serve times using '%D'? You'll have discovered that they aren't a good index of your server's performance, because they depend more on the client's connection speed, computer and browsing habits than on the speed of your server. mod_log_firstbyte is a module for Apache 2.0 which allows you to log the time between each request being read and the first byte of the response served. Unlike the total serve time, this index of performance tells you how long Apache actually spent loading the file off the disk or executing your script: it's independent of client connection speed. It makes a great performance benchmark for your server!

The crawl utility starts a depth-first traversal of the web at the specified URLs. It stores all JPEG images that match the configured constraints. Crawl is fairly fast and allows for graceful termination. After terminating crawl, it is possible to restart it at exactly the same spot where it was terminated. Crawl keeps a persistent database that allows multiple crawls without revisiting sites. The main reason for writing crawl was the lack of simple open source web crawlers. Crawl is only a few thousand lines of code and fairly easy to debug and customize. Some of the main features: - Saves encountered JPEG images - Image selection based on regular expressions and size contrainsts - Resume previous crawl after graceful termination - Persistent database of visited URLs - Very small and efficient code - Supports robots.txt

This perl module provides an Active Server Pages port to the Apache HTTP Server with perl as the host scripting language. Active Server Pages is a web application platform that originated with the Microsoft IIS server. Under Apache for both Win32 and Unix, it allows a developer to create dynamic web applications with session management and perl code embedded in static html files. This is a portable solution, similar to ActiveState PerlScript and MKS PScript implementation of perl for IIS ASP. Work has been done and will continue to make ports to and from these other implementations as smooth as possible. This module works under the Apache HTTP Server with the mod_perl module enabled. See http://www.apache.org and http://perl.apache.org for further information. For database access, ActiveX, and scripting language issues, please read the FAQ section. http://search.cpan.org/dist/Apache-ASP/

The Apache::ConfigParser module is used to load an Apache configuration file to allow programs to determine Apache's configuration directives and contexts. The resulting object contains a tree based structure using the Apache::ConfigParser::Directive class, which is a subclass of Tree::DAG_node, so all of the methods that enable tree based searches and modifications from Tree::DAG_Node are also available. The tree structure is used to represent the ability to nest sections, such as <VirtualHost>, <Directory>, etc. Apache does a great job of checking Apache configuration files for errors and this modules leaves most of that to Apache. This module does minimal configuration file checking. The module currently checks for: Start and end context names match The module checks if the start and end context names match. If the end context name does not match the start context name, then it is ignored. The module does not even check if the configuration contexts have valid names.

CGI::XMLApplication is a CGI application class, that intends to enable perl artists to implement CGIs that make use of XML/XSLT functionality, without taking too much care about specialized errorchecking or even care too much about XML itself. It provides the power of the XML::LibXML/XML::LibXSLT module package for content deliverment. As well CGI::XMLApplication is designed to support project management on code level. The class allows to split web applications into several simple parts. Through this most of the code stays simple and easy to maintain. Throughout the whole lifetime of a script CGI::XMLApplication tries to keep the application stable. As well a programmer has not to bother about some of XML::LibXML/XML::LibXSLT transformation pitfalls.

This module provides all of the same functionality of WWW::Mechanize, but adds support for plugins using Module::Pluggable; this means that any module named WWW::Mechanize::Plugin::whatever... will be found and loaded when WWW::Mechanize::Pluggable is loaded. Big deal, you say. Well, it becomes a big deal in conjunction with WWW::Mechanize::Pluggable's other feature: plugin hooks. When plugins are loaded, their import() methods can call WWW::Mechanize::Pluggable's prehook and posthook methods. These methods add callbacks to the plugin code in WWW::Mechanize::Pluggable's methods. These callbacks can act before a method or after it, and have to option of short-circuiting the call to the WWW::Mechanize::Pluggable method altogether. These methods receive whatever parameters the WWW::Mechanize::Pluggable methods received, plus a reference to the actvive Mech object. All other extensions to WWW::Mechanize::Pluggable are handled by the plugins.

The Servlet API for Perl (libservlet) is a formulation of the Java (TM) Servlet API in Perl. While the servlet concept originated with Java (TM), its component model is quite natural for Perl as well. By writing servlet applications and deploying them in a servlet container, application authors can spare themselves the effort of writing commonly needed web application infrastructure components for each new project. Furthermore, servlet applications are portable between deployment environments; they can be executed in any servlet container using any process model with only a few configuration changes and no application code changes. Servlet applications are insulated from changes in vendor or platform and are able to portably take advantage of standard web infrastructure services offered by any servlet container.

thttpd is a simple, small, portable, fast, and secure HTTP server. - Simple: It handles only the minimum necessary to implement HTTP/1.1. - Small: It also has a very small run-time size, since it does not fork and is very careful about memory allocation. - Portable: It compiles cleanly on SunOS 4.1.x, Solaris 2.x, BSD/OS 2.x, Linux 1.2.x, and OSF/1 (on a 64-bit Alpha). - Fast: In typical use it's about as fast as the best full-featured servers (Apache, NCSA, Netscape). Under extreme load it's much faster. - Secure: It goes to great lengths to protect the web server machine against attacks and breakins from other sites. It also has one extremely useful feature (URL-traffic-based throttling) that no other server currently has.

Transmission Web Interface (Clutch) is a WebUI for the Transmission BitTorrent client. It allows you to manage your torrents from anywhere you can access the internet, and runs on OS X and various flavors of *nix. It provides most of the basic features of the desktop client, including torrent upload, torrent start/stop, file path selection, speed limiting etc. Transmission has been built from the ground up to be a lightweight, yet powerful BitTorrent client. Its simple, intuitive interface is designed to integrate tightly with whatever computing environment you choose to use. Transmission strikes a balance between providing useful functionality without feature bloat. Furthermore, it is free for anyone to use or modify. You will need to install either transmission-daemon, transmission-gtk2 or both to use WebUI.

AWS stands for Ada Web Server, but it is more than just another webserver... AWS is a complete framework to develop web based applications. The main part of the framework is the embedded web server. This small yet powerful web server can be embedded into your application so your application will be able to talk with a standard web browser such as Microsoft Internet Explorer or Netscape Communicator. Around this web server, a lot of services have been developed. The framework includes: * seb parameters module * session server * SOAP support * WSDL generation from Ada * template parser * AJAX support * HTTPS/SSL support * large server support * virtual hosting support * server push * directory browser * status page * log module * hotplug module * light communications API * configuration API * client API * web page service * SMTP support * LDAP support * Jabber support