Panther is a lightweight, modular Java application server, suitable for embedding in a web server.

The intention of the project is not to duplicate all the functionality found in a J2EE app server, rather just some of the most commonly used features (Note: panther was formerly known as Wicker).

1. Panther is not trying to be a full application server, rather it provides a limited subset of services that most app servers provide.
2. Most app servers seem to be huge monolithic behemoths where its all or nothing. If you want one service, then you pretty much need them all. Even where you can modify the configuration to only include the services you require, based upon our experience, many projects dont.
3. Many projects only use a microscopic subset of the features an app server provides. This is particularly true if you want to be cross-appserver/cross-platform, so a modular app server, where you include the bits you want, makes a lot of sense (at least to us). This is, of course, rather similar to the argument certain luminaries have used in the past against the feature bloat in Office software like Word.
4. There isnt another open source app server out there that does what we want (or that we could get working just the way we wanted).

Here are some key features of "Panther":

· A Stateless Session Bean container.
· Note 1: SSBs were not pooled prior to version 0.9.1, so there -was- a single instance of each EJB in the container. There didnt seem to be any overhead/negative impact doing things this way, except that the beans are truly/completely stateless -- if youre writing code with this is mind, then you shouldnt have any problems, but we recommend using the latest release anyway.
· Note 2: At time of writing only the ejbCreate method has been implemented in panther (the other ejb* methods are not currently called).
· deployment and configuration by Jython
· transaction manager -- linked to the data source service. This only works with JDBC data sources, and has only been tested with Postgres so far. (Note, transactions do not cross VM boundaries.)
· a basic messaging service (multicast, broadcast and lightweight reliable multicast options available)
· jdbc distributed caching service, codenamed c3d -- basically a jdbc driver that caches selects to reduce load on the database and to improve performance (slightly)
· a python-scripted (well, jython) telnet management console
· example mail and datasource (using Jakarta DBCP) python scripts are also included

Limitations:

· You cannot currently pass parameters to ejbCreate, or indeed include parameters in your home create methods.
· transaction support is currently extremely limited. The transaction manager is a basic service written to get us going -- "Required", "Supports" and "NotSupported" should (hopefully) work as advertised, anything else (i.e. "RequiresNew") may get unpredictable results. Were working on the transaction service at the moment.

Whats New in This Release:

NOTES

· Fix a bunch of bugs I discovered this morning with the build process, demo, etc

CHANGES

· Reorganised the doc directory. Moved example files to doc/examples
· added jetty.sh, start.sh and stop.sh, to be used for running jetty5. Create a bin dir in $JETTY_HOME, put both files there (along with panther in the root of jetty home) and run start.sh to use.
· tidied up readme.txt

BUG FIXES

· added a Makefile for the simple demo. Fixed a bug with the ant build. Moved the jsp to a plain servlet
· distribution tars werent created with the correct directory (shouldve had a root panther dir).

Baghira is a native style for QT/KDE.

The name refers to the Panther of Kiplings famous Jungle Book (German spelling)

You will probably rather know the Disney version...

Basically its a perky imitation of Apples OSX look.

Installation:

tar -xjf baghira.tar.bz2
cd baghira/baghira
./configure --prefix=`kde-config --prefix` --disable-debug [--enable-final]
(!!!BEGINNERS: the direction of the accents is _important_ (top-left to bottom-right), the rectangular brackets mean [this is optional] - dont type them!!!)
make
and finally as root:
make install

XQDE need only Qt4 and will support bindings for KDE and Gnome applications. XQDE is faster small and join the power of KXDocker to all new desktop.

XQDE, you can call it "xcode" is new idea for Desktop Environment. Its Qt4 based and it will gain all Compiz (Beryl) power.

Here are some key features of "XQDE":

· XQDE can be aligned on left, right, bottom ( top is working in progres)
· XRender or Qt4 hight speed render can be choosed
· 5 times smaller size code than KXDocker 1.x
· like KXDocker: XQDE gain speed by using CPU less "panther" engine

Whats New in This Release:

· Support was added for Xinerama displacement. Now you can run multiple instances of XQDE on your screen.

TMSNC is a textbased (console) MSN client written in C. TMSNC should work on most Unix (Linux, BSD, MacOS) compatible operating systems.

Textbased MSN Client projects main goal is to create a client like MSN Messenger (with sound, webcam and file transfer support), but without any graphical features.

TMSNC is an opensource project which is released under the IR Public Domain License which basically is a modification of the BSD license.

It has been tested to work on

· OpenBSD/PowerPC 3.7
· Gentoo Linux 2005.1
· CRUX Linux 2.0
· MacOS X 10.3.9 (Panther)
· Debian Linux 3.1
· Slackware Linux 9.1
· RedHat Linux 9
· Fedora Core
· SuSE 9.0 Professional
· Solaris 8
· Mandrake 10.0

Osmose is a tool to prepare multimedia presentations. It is a free software distributed under the GPL license.

Osmose project was written in Java and has been tested under Mac OS X (Panther and Tiger), Linux, and Windows XP with Java 1.4.2.

Osmose allows you to print the presentations and to visualize them on the screen and on the Web in HTML (under Mac OS X, it is also easy to create PDF files from your presentations).

Osmose is based on a research work that proposes a new way to create digital documents. We invite everyone to leave the WYSIWYG mode to a more complete way of working, that articulates: working on the content, adding multimedia files, and working on the style using a graphic theme.

IaxComm is an Open Source softphone (VOIP) using iax protocol. iaxComm works on Win32, Linux and Mac OS X (Panther) systems.

The source code is in the simpleclient/iaxcomm subdirectory of the iaxclient source code tree, which is is available via SVN.

Here are some key features of "iaxcomm":

· iLBC support
· speex support
· Music on Hold.
· Blind Transfer.
· Custom Ringtones per CallerID
· Speakerphone mode.
· Register with multiple servers (ie enterprise server and iaxtel).
· Multiple call appearances.
· User selectable audio devices.
· User defined ringtones.
· Autoanswer intercom calls (with password protection).
· Registration with an asterisk server prior to dialing is no longer required.
· Simplified Directory dialogs.
· Incoming callers automatically added to phone book.

gatling is a high-performance HTTP and FTP server. It is small, fast, and scalable, and uses platform-specific performance and scalability APIs.

It supports connection keep-alive, el-cheapo virtual domains (similar to thttpd), IPv6, and Content-Range (not the full specs, just a-b or a-byte ranges).

Here are some key features of "gatling":

· Small! (100k static Linux-x86 binary with HTTP and FTP support)
· Fast! (measure for yourself, please)
· Scalable! (see this document, measured using tools that are included in the gatling distribution.
· Uses platform-specific performance and scalability APIs on Linux 2.4, Linux 2.6, NetBSD current (2.0+), FreeBSD 4+, OpenBSD 3.4+, Solaris 9+, AIX 5L, IRIX 6.5+, MacOS X Panther+, HP-UX 11+
· connection keep-alive
· el-cheapo virtual domains (similar to thttpd)
· IPv6 support
· Content-Range (not the full specs, just a-b or a- byte ranges)
· transparent content negotiation (will serve foo.html.gz if foo.html was asked for and browser indicates it understands deflate)
· With optional directory index generation
· Will only serve world readable files (so you dont export files accidentally)
· Supports FTP and FTP upload as well (upload only to world writable directories and the files wont be downloadable unless you chmod a+r them manually)
· CGI support for HTTP
· El-cheapo .htaccess support (see README.htaccess)
· Quick-and-dirty SSL/TLS support (see README.tls)

Whats New in This Release:

· A pipelining bug was fixed.
· HTTP headers are now sent to CGIs as HTTP_FOO=bar environment variables.
· Cleanups were made for GCC 4.
· Temporary fallback redirects were added.
· CGI slaves are now only forked if the -C option is given on the command line.
· IRIX compatibility was established.

reSIProcate software consists of a stack and a small collection of applications. The reSIProcate stack is currently used in several commercial products and is considered very stable.

reSIProcate is ideally suited to individuals or companies that are implementing one of the following SIP applications:

· Phones (eg. embedded);
· Softphones (any platform);
· Gateways;
· Proxies;
· B2BUAs, or;
· IM / Presence Servers or Clients.

Here are some key features of "reSIProcate":

· Uses the VOCAL license (BSD like);
· UDP, TCP, TLS transports;
· A full implementation of the 3261 transaction state machine;
· A lazy parser - only parse headers when the application requests them;
· A strongly typed interface;
· The parser is compliant with the current RFCs;
· An Object-Oriented SDP parser and encoder;
· Support for SipFrag;
· Support for rport;
· Object Oriented C++ interface to the messages;
· Asynchronous DNS library (ares from MIT);
· Fast performance: > ~500 transactions per second on an Intel P4;
· Ability to add new headers and parameters without rebuilding the stack;
· MIME and multipart-MIME contents;
· S/MIME
· Single-threaded or multi-threaded (thread-safe stack);
· One library with only two external dependencies:
· ares - DNS Resolver
· openssl - Security (for TLS)
· Multiple SIP stacks in the same application;
· Support for shutting down a SIP stack without exiting the application
· IPv6 support in the parser and DNS ;
· Full NAPTR and SRV support (support RFCs: 3261, 3263, 2915, 2782) ;
· Full asynchronous DNS support in Windows ;
· Support for multi-homed hosts ;
· Builds and runs on Windows and most Unixes. reSIProcate has been built and tested on:
· GNU/Linux 2.4, 2.5 ;
· Mac OS/X 10.2 (Panther) ;
· Solaris 8 and 9, and ;
· Windows XP and 2003 Server ;
· (most things with modern C++ compilers), and;
· Easy to plug-in new transport protocols.

Whats New in This Release:

· A bug that would cause the stack to crash if it received a request with a single empty Via header was fixed.

mod_clamav is a virus scanning module which uses the Clam Antivirus (clamav) package to scan Web traffic for viruses. Apache 2 introduces filters, which allow to modify content generated by some other module. mod_clamav is an Apache 2 filter which scans the content delivered by the proxy module (mod_proxy) for viruses using the Clamav virus scanning engine.

mod_clamav was written and is currently maintained by Andreas Müller, it is distributed under the GNU General Public License, see the file COPYING in the distribution for details.

This document describes Version 0.21 of mod_clamav. This version can be downloaded from http://software.othello.ch/mod_clamav/mod_clamav-0.21.tar.gz. The most current version will always be available at http://software.othello.ch/mod_clamav/.

Before installing mod_clamav, make sure you have Clamav properly installed. The module is of only limited use if the proxy module is not available to apache, which is not built by default. So you may want to go back to your Apache compilation and adjust the options to configure so that the proxy module to be built.

The only configuration option necessary for mod_clamav is --with-apache=/your/apache2/directory. So installing the module usually takes the familiar steps

./configure --with-apache=/usr/local/apache2
make
make install

mod_clamav can produce extensive log messages, but as they may slow down the module, log messages at debug level are only produced if the module is compiled with debugging enabled. Add -DCLAMAV_DEBUG to your CFLAGS environment variable to enable debuggin:

CFLAGS="-DCLAMAV_DEBUG"
export CFLAGS

mod_clamav has so far been tested on Linux, Solaris and Mac OS X (the latter only in local mode on Jaguar, Clamav 0.70 on Panther finds a suitable pthreads implementation and compiles the daemon, and mod_clamav seems to work in daemon mode on Panter, but I have not fully tested it). If you succeed to install the module on some other platform, please keep the maintainer updated.

Some initial testing on FreeBSD revealed some permission problems, but mod_clamav seems to work if the apache server and clamd run with the same uid.

mod_clamav is an Apache 2 filter, so there is no hope that it will ever be usable with Apache 1. Filters were introduced in Apache 2 to inspect and modify content delivered by some other module.

mod_clamav takes the output of the proxy module, and scans it for viruses using the Clamav library (local mode) or the Clamav daemon (daemon mode). This means that in local mode, the virus scanning engine is part of the apache process, thus virus scanning does not take an extra round-trip to a virus scanning proxy, as with many other virus scanning products.

The clamav library could work entirely inside main memory, but this would cause a problem for large downloads: they could eat up all memory starving the machine in the process. Hence mod_clamav writes the data to a file, the location is configurable with the ClamavTmpdir directive. If file IO is a problem, the temporary files can be placed on a ramdisk.

Long downloads create a special dilemma for a virus scanning proxy: the proxy should not send anything to the browser before it has made sure the object is virus free, but the browser may think the server has a problem if no data is transmitted for a long time. mod_clamav therefore sends one byte every minute (or less if you prefer) of the file being downloaded to the browser. This is enough to keep the browser happy.

Some platforms do not support daemon mode, because the Clamav daemon (which uses pthreads), is not available for them. One example is Mac OS X, on which mod_clamav can only be used in local mode.

One problem with browsers is that the decide to time out if the proxy does not send any data to them. So mod_clamav sends a single byte every minute, even before anything has been checked for viruses. This has the side effect that no HTML error message can be displayed to the client if a byte has been sent already. If the transfer from the server completes within the first minute, i.e. before the first trickle byte is sent to the browser, mod_clamav sends an HTML error message (new in 0.9).