The mission of the Apache Portable Runtime (APR) project is to create and maintain software libraries that provide a predictable and consistent interface to underlying platform- specific implementations. The primary goal is to provide an API to which software developers may code and be assured of predictable if not identical behaviour regardless of the platform on which their software is built, relieving them of the need to code special-case conditions to work around or take advantage of platform-specific deficiencies or features.
Trojan scan is a simple shell script that allows for simple but relatively effective checking for trojans, rootkits and other malware that may be using your server and network for unwanted (and possibly illegal) purposes. It works by listing all processes that use the Internet with the lsof command (using -Pni flags). This list is then transformed into signatures in the form of process_name:port_number:user. These signatures then are matched against the allowed process defined in the configuration. If any signatures of running processes are found that do not match the allowed signatures, an email report is sent including ps, ls, and optional lsof output.
BitNami LAMPStack Native Installer is an easy-to-install environment to develop and deploy PHP applications. It includes pre-configured, ready-to-run versions of Apache, MySQL, PHP, and phpMyAdmin. Amazon AWS PHP SDK makes it easier to develop PHP applications that run on Amazon Web Services. The AWS PHP SDK includes the AWS PHP library, code samples, and documentation.
Universal File Mover (UFM) manages the transfer of files. The user combines a series of Action commands to create the UFM Workflow XML file. These Action commands define which actions are to be taken, the order of the actions, and how errors are to be handled. UFM processes the Action commands as per the UFM Workflow XML file. UFM currently contains 40 Action commands. These action commands fall into five categories: WebSphere MQ Actions, Network Actions, File Actions, Control Actions, and Other Actions. UFM can transfer files in one of five ways, using WebSphere MQ, FTP, SFTP, SCP, or HTTP.
The Apache Traffic Server (TS or ATS) is a modular, high-performance reverse proxy server, generally comparable to Squid. It was created by Inktomi, and distributed as a commercial product called the Inktomi Traffic Server, before Inktomi was acquired by Yahoo!. Traffic Server has been actively used inside of Yahoo for over 4 years, serving billions of requests every day. As of fall 2009, Traffic Server is an Open Source project, and in April 2010 the Apache Traffic Server was promoted to a top-level project of the ASF.
Ding is a PHP framework that provides dependency injection (by Setter, Constructor, and Method), Aspect Oriented Programming, XML, YAML, Events support, and some JSR 250/330 annotations as bean definition providers, lightweight, can be deployed as a PHAR file, simple, and quick MVC, syslog, TCP client and server with non-blocking sockets, timers, and custom error, signal, and exception handling, PAGI integration (for the Asterisk gateway interface), and PAMI integration (for Asterisk management). It is similar to Java's Seasar and Spring.
JasperStarter is a commandline launcher and batch compiler for JasperReports. It can run any JasperReport that needs a JDBC data source or empty data source, use any database for which a JDBC driver is available, execute reports that need runtime parameters, print directly to the system default or a given printer, optionally show a printer dialog to choose a printer, optionally show a print preview, export to file in the PDF, RTF, .docx, .odt, and HTML formats, export multiple formats in one commanding call, print and export in one commanding call, and integrate in non-Java applications (for example PHP, Python) A binary executable is available for Windows. The string, int, and date parameter types are supported.
WeOCR is a platform for Web-enabled OCR (Optical Character Reader/Recognition) systems. It enables people to use character recognition over networks. A WeOCR server receives document images from users, recognizes text in the images, and returns recognition results to the users. WeOCR does not have its own character recognition engine. Instead, it is intended to accommodate various existing character recognition engines.