0.7.1
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 90
acoc 0.7.1
acoc is an arbitrary command output colourer. more>>
acoc is an arbitrary command output colourer.
Ever wondered why the output of your favourite UNIX/Linux commands is still displayed in black-and-white after all these years?
Ever had to search back through your scroll-buffer in search of gcc errors and salient information to tell you what went wrong with your programs execution?
acoc is a regular expression based colour formatter for programs that display output on the command-line. It works as a wrapper around the target program, executing it and capturing the stdout stream. Optionally, stderr can be redirected to stdout, so that it, too, can be manipulated.
acoc then applies matching rules to patterns in the output and applies colour sets to those matches. A picture is worth a thousand words, so look at the sample screenshots in the next section.
<<lessEver wondered why the output of your favourite UNIX/Linux commands is still displayed in black-and-white after all these years?
Ever had to search back through your scroll-buffer in search of gcc errors and salient information to tell you what went wrong with your programs execution?
acoc is a regular expression based colour formatter for programs that display output on the command-line. It works as a wrapper around the target program, executing it and capturing the stdout stream. Optionally, stderr can be redirected to stdout, so that it, too, can be manipulated.
acoc then applies matching rules to patterns in the output and applies colour sets to those matches. A picture is worth a thousand words, so look at the sample screenshots in the next section.
Download (0.043MB)
Added: 2006-04-18 License: GPL (GNU General Public License) Price:
1284 downloads
Jolt 0.7.1
Jolt is a Java Virtual Machine Daemon. more>>
Jolt is a Java Virtual Machine Daemon. This program provides a means to invoke the JDK tools javac, javadoc, and jar from the command line while reusing the same JVM instance across invocations.
Jolt daemon is intended primarily for use as a helper tool to make compilation of Java code with make as fast as (and potentially faster than) with Jakarta Ant.
It can also be used to run arbitrary Java programs (as with java); this is particularly useful for command-line utilities that are run over and over, where the cost of launching the JVM each time would be prohibitive (or at the very least, annoying).
Usage:
The `runjolt shell script can be used as a wrapper for the `jolt binary. It checks for the presence of the JAVA_HOME environment variable (which should be set to the top-level installation directory of JDK 1.4.0 or later) and augments LD_LIBRARY_PATH accordingly before invoking `jolt proper.
<<lessJolt daemon is intended primarily for use as a helper tool to make compilation of Java code with make as fast as (and potentially faster than) with Jakarta Ant.
It can also be used to run arbitrary Java programs (as with java); this is particularly useful for command-line utilities that are run over and over, where the cost of launching the JVM each time would be prohibitive (or at the very least, annoying).
Usage:
The `runjolt shell script can be used as a wrapper for the `jolt binary. It checks for the presence of the JAVA_HOME environment variable (which should be set to the top-level installation directory of JDK 1.4.0 or later) and augments LD_LIBRARY_PATH accordingly before invoking `jolt proper.
Download (0.11MB)
Added: 2005-12-09 License: GPL (GNU General Public License) Price:
1416 downloads
QPong 0.7.1
QPong project is another clone of the game pong. more>>
QPong project is another clone of the game "pong".
It features some nice graphics and is very flexible.
You can configure the images, sizes, speeds, and shapes of the pads and balls.
Most importantly, its fun to play.
<<lessIt features some nice graphics and is very flexible.
You can configure the images, sizes, speeds, and shapes of the pads and balls.
Most importantly, its fun to play.
Download (MB)
Added: 2006-11-16 License: GPL (GNU General Public License) Price:
1072 downloads
Zabit 0.7.1
Zabit is a content/attachment filter for qmail. more>>
Zabit is a content/attachment filter for qmail. Its been coded in C language for performance reasons. Zabit project consists of two main components, zabit and zabit-wrp.
Zabit does content filtering and attachment control, whereas zabit-wrp is designed to allow a virus-scanner to co-exist with zabit.
Installation:
Edit conf-locale file.
This file includes locale information for case sensitivity. And run
./configure
make
make install
Enhancements:
- Added configure script
<<lessZabit does content filtering and attachment control, whereas zabit-wrp is designed to allow a virus-scanner to co-exist with zabit.
Installation:
Edit conf-locale file.
This file includes locale information for case sensitivity. And run
./configure
make
make install
Enhancements:
- Added configure script
Download (0.017MB)
Added: 2005-10-18 License: GPL (GNU General Public License) Price:
1467 downloads
OOWeb 0.7.1
OOWeb is a lightweight, embedded HTTP server for Java applications. more>>
OOWeb is a lightweight, embedded HTTP server for Java applications that maps objects to URL directories, methods to pages and form/querystring arguments as method parameters.
This allows for unparalleled ease in creating, deploying and testing web applications and most importantly, its fun to use!
This project was unashamedly inspired by CherryPy.
Main features:
- GET/POST
- HTTP Sessions
- Cookies
- Logging
- Static content
- Replicated sessions to transparently distribute user sessions to all OOWeb instances on a network. Requires zero configuration.
- Security with either HTTP BASIC or forms based authentication.
- Very portable (pure Java and compatible with Sun JDK 1.4, Kaffe, JamVM, SableVM, GIJ/GCJ, etc.)
- Incredibly lightweight (v0.5 is just 50k) with no external dependencies
- Quick to learn - get a basic dynamic website running from scratch in 10 minutes
Enhancements:
- This release was updated to JUnit 4.3.
- Some tidying and polishing of JavaDoc, logging, etc. was undertaken.
- The server now ensures that user exceptions result in HTTP 500 rather than HTTP 200 response codes.
- Caching was implemented for the @Cacheable annotation.
- It provides a trivial memory backed cache for responses to cacheable methods.
- Samples were restructured and a groovy "Worldapp" sample was added.
<<lessThis allows for unparalleled ease in creating, deploying and testing web applications and most importantly, its fun to use!
This project was unashamedly inspired by CherryPy.
Main features:
- GET/POST
- HTTP Sessions
- Cookies
- Logging
- Static content
- Replicated sessions to transparently distribute user sessions to all OOWeb instances on a network. Requires zero configuration.
- Security with either HTTP BASIC or forms based authentication.
- Very portable (pure Java and compatible with Sun JDK 1.4, Kaffe, JamVM, SableVM, GIJ/GCJ, etc.)
- Incredibly lightweight (v0.5 is just 50k) with no external dependencies
- Quick to learn - get a basic dynamic website running from scratch in 10 minutes
Enhancements:
- This release was updated to JUnit 4.3.
- Some tidying and polishing of JavaDoc, logging, etc. was undertaken.
- The server now ensures that user exceptions result in HTTP 500 rather than HTTP 200 response codes.
- Caching was implemented for the @Cacheable annotation.
- It provides a trivial memory backed cache for responses to cacheable methods.
- Samples were restructured and a groovy "Worldapp" sample was added.
Download (0.36MB)
Added: 2007-06-14 License: LGPL (GNU Lesser General Public License) Price:
865 downloads
BEAST 0.7.1
Beast is a powerful music composition and modular synthesis application. more>>
Beast project is a powerful music composition and modular synthesis application.
Beast is a powerful music composition and modular synthesis application released as free software under the GNU GPL and GNU LGPL, that runs under unix. It supports a wide range of standards in the field, such as MIDI, WAV/AIFF/MP3/OggVorbis/etc audio files and LADSPA modules.
It has excellent technical abilities like multitrack editing, unlimited undo/redo support, real-time synthesis support, 32bit audio rendering, full duplex support, multiprocessor support, precise timing down to sample granularity, on demand loading of partial wave files, on the fly decoding and full scriptability in scheme.
The plugins, synthesis core and the user interface are actively being developed and translated into a variety of languages, regularly assimilating user feedback.
<<lessBeast is a powerful music composition and modular synthesis application released as free software under the GNU GPL and GNU LGPL, that runs under unix. It supports a wide range of standards in the field, such as MIDI, WAV/AIFF/MP3/OggVorbis/etc audio files and LADSPA modules.
It has excellent technical abilities like multitrack editing, unlimited undo/redo support, real-time synthesis support, 32bit audio rendering, full duplex support, multiprocessor support, precise timing down to sample granularity, on demand loading of partial wave files, on the fly decoding and full scriptability in scheme.
The plugins, synthesis core and the user interface are actively being developed and translated into a variety of languages, regularly assimilating user feedback.
Download (5.5MB)
Added: 2006-12-28 License: GPL (GNU General Public License) Price:
1031 downloads
CLISH 0.7.1
CLISH is a modular framework for implementing a CISCO-like CLI on a Unix system. more>> <<less
Download (0.48MB)
Added: 2006-10-13 License: BSD License Price:
1110 downloads
Picard 0.7.1
Picard is the Next-Generation MusicBrainz Tagger. more>>
Picard is the Next-Generation MusicBrainz Tagger. The project code-named Picard is the next generation MusicBrainz tagging application.
This new tagging concept is Release oriented, as opposed to track oriented like the ClassicTagger was.
Picard is written in Python, which is a cross-platform language - this allows the same code to run both on Windows and on Linux.
<<lessThis new tagging concept is Release oriented, as opposed to track oriented like the ClassicTagger was.
Picard is written in Python, which is a cross-platform language - this allows the same code to run both on Windows and on Linux.
Download (0.032MB)
Added: 2006-10-05 License: GPL (GNU General Public License) Price:
1114 downloads
Tapiir 0.7.1
Tapiir is a simple and flexible audio effects processor. more>>
Tapiir is a simple and flexible audio effects processor, inspired on the classical magnetic tape delay systems used since the early days of electro-acoustic music composition.
Tapiir project provides a graphical user interface consisting of six delay lines, or "taps", which can introduce an almost arbitrarily big or small delay to their inputs and can be feed back to each other.
A wide set of effects can be easily achieved by properly configuring and connecting the delay lines: complex echo patterns, resonances, filtering, etc. Delays, interconnections and gains can all be controlled in real time.
TAPIIR internal processing modules consist of six delay-lines, each with a mixer at its input and a gain control at its output, and a stereo output mixer. Stereo input from an external source, typically a musical instrument, is routed to all input mixers. In addition to this, the output of each delay line is also routed to the input mixers of all delay lines, including itself. Figure 1 shows the diagram of TAPIIRs internals.
This cross-feeding of audio signals throughout the system of delay-lines and mixers, allows the user to create a very large variety of stereo delay effects. Very simple echos or ping-pong effects can be achieved easily, but more complex effects such as early reflection echos, reverbs, complex rhythmic and arrhythmic patterns and even Karplus-Strong like synthesis is also possible. It is important to observe, that these more complex effects are only possible by using sample accurate processing.
This article appears in Proceedings of the COST G-6 Conference on Digital Audio Effects (DAFX-01), Limerick, Ireland, December 6-8, 2001
Sample accuracy
Conventional hardware effect processors are often rather limited in the lenght of there delay-lines. It is unusual to encounter accuracy higher than 1 msec, and even 10 msec is used frequently, and maximum delay-lenght are limited as well.
Obviously, this limitation in hardware effect processors is deliberate, both out of technical concerns or marketing. Most users are not interested in higher accuracy, and the standard user interface of hardware effects processors - buttons or at the most an alpha-dial - would make it a painful job to adjust. Also, one can imagine that lower accuracy means less computational cost, and therefore lower overall cost of the effect processing hardware.
For advanced users however, this limitation can be annoying. Of course, many of the effects obtained with very short delay times, such as reverb or filtering, are usually also implemented in the same hardware, but it can be very interesting to combine all these with longer delay-time effects; it would be necessary to use several processors connected together to do this.
The implementation of TAPIIR, however, is sample accurate. This means that extremely short delay times can be used, 0.023 msec when using a sample-rate of 44100 Hz. In addition to this fine control over delay-lengths, the sample accuracy is also implented for feedback and even cross-feeding between the various delay-lines, This is achieved by the fact that the internal processing core of TAPIIR is written in such a way, that the input and output values of the delay-lines and mixers are passed on 1 at a time, instead of buffer-by-buffer.
Filtering with delays
Obviously, the effects obtained by sample accurate processing of delay-lines go far beyond the simple echo effects. This includes the creation of FIR filters and - using feedback - IIR filters (this has been the inspiration for the name TAPIIR). In these cases, the mixer gains function as filter coefficients. This means that TAPIIR can efficiently be used for filtering, with flexible filter design. In a future version, TAPIIR could contain a pole/zero editor that automatically sets the mixer values to create the corresponding filter.
The maximum delay-length that can be achieved is only limited by the physical RAM memory of the system TAPIIR runs on. To give an example, with 32 MB of free memory, a total delay-length of more than 6 minutes can be used. While this might seem rather useless for normal effect processing, it clearly has musical applications. Several compositions have been written that make use of long delay times. Originally performed with the use of tape-delays, they could take great profit of the use of digital techniques for sound quality. The use of hard disk space with sufficient fast access would take away time limitation even more.
Delay-length control
The graphical user interface of TAPIIR allows the user to take full advantage of the delay-length accuracy, but at the same time it tries to maintain user-friendly and manageable, by offering value-sliders for larger scales as well. Delay-time can be entered in time in seconds in number of samples. Sliders control the digits of the delay-length, with an accuracy of 5 decimals. An additional feature is the use of tempo/signature. In that case, delay-length in not represented in seconds, but in beats, and the sliders control the subdivision of beats according to the signature. Obviously, in many circumstances this representation is a lot more useful, in a musical sense, than time in seconds.
<<lessTapiir project provides a graphical user interface consisting of six delay lines, or "taps", which can introduce an almost arbitrarily big or small delay to their inputs and can be feed back to each other.
A wide set of effects can be easily achieved by properly configuring and connecting the delay lines: complex echo patterns, resonances, filtering, etc. Delays, interconnections and gains can all be controlled in real time.
TAPIIR internal processing modules consist of six delay-lines, each with a mixer at its input and a gain control at its output, and a stereo output mixer. Stereo input from an external source, typically a musical instrument, is routed to all input mixers. In addition to this, the output of each delay line is also routed to the input mixers of all delay lines, including itself. Figure 1 shows the diagram of TAPIIRs internals.
This cross-feeding of audio signals throughout the system of delay-lines and mixers, allows the user to create a very large variety of stereo delay effects. Very simple echos or ping-pong effects can be achieved easily, but more complex effects such as early reflection echos, reverbs, complex rhythmic and arrhythmic patterns and even Karplus-Strong like synthesis is also possible. It is important to observe, that these more complex effects are only possible by using sample accurate processing.
This article appears in Proceedings of the COST G-6 Conference on Digital Audio Effects (DAFX-01), Limerick, Ireland, December 6-8, 2001
Sample accuracy
Conventional hardware effect processors are often rather limited in the lenght of there delay-lines. It is unusual to encounter accuracy higher than 1 msec, and even 10 msec is used frequently, and maximum delay-lenght are limited as well.
Obviously, this limitation in hardware effect processors is deliberate, both out of technical concerns or marketing. Most users are not interested in higher accuracy, and the standard user interface of hardware effects processors - buttons or at the most an alpha-dial - would make it a painful job to adjust. Also, one can imagine that lower accuracy means less computational cost, and therefore lower overall cost of the effect processing hardware.
For advanced users however, this limitation can be annoying. Of course, many of the effects obtained with very short delay times, such as reverb or filtering, are usually also implemented in the same hardware, but it can be very interesting to combine all these with longer delay-time effects; it would be necessary to use several processors connected together to do this.
The implementation of TAPIIR, however, is sample accurate. This means that extremely short delay times can be used, 0.023 msec when using a sample-rate of 44100 Hz. In addition to this fine control over delay-lengths, the sample accuracy is also implented for feedback and even cross-feeding between the various delay-lines, This is achieved by the fact that the internal processing core of TAPIIR is written in such a way, that the input and output values of the delay-lines and mixers are passed on 1 at a time, instead of buffer-by-buffer.
Filtering with delays
Obviously, the effects obtained by sample accurate processing of delay-lines go far beyond the simple echo effects. This includes the creation of FIR filters and - using feedback - IIR filters (this has been the inspiration for the name TAPIIR). In these cases, the mixer gains function as filter coefficients. This means that TAPIIR can efficiently be used for filtering, with flexible filter design. In a future version, TAPIIR could contain a pole/zero editor that automatically sets the mixer values to create the corresponding filter.
The maximum delay-length that can be achieved is only limited by the physical RAM memory of the system TAPIIR runs on. To give an example, with 32 MB of free memory, a total delay-length of more than 6 minutes can be used. While this might seem rather useless for normal effect processing, it clearly has musical applications. Several compositions have been written that make use of long delay times. Originally performed with the use of tape-delays, they could take great profit of the use of digital techniques for sound quality. The use of hard disk space with sufficient fast access would take away time limitation even more.
Delay-length control
The graphical user interface of TAPIIR allows the user to take full advantage of the delay-length accuracy, but at the same time it tries to maintain user-friendly and manageable, by offering value-sliders for larger scales as well. Delay-time can be entered in time in seconds in number of samples. Sliders control the digits of the delay-length, with an accuracy of 5 decimals. An additional feature is the use of tempo/signature. In that case, delay-length in not represented in seconds, but in beats, and the sliders control the subdivision of beats according to the signature. Obviously, in many circumstances this representation is a lot more useful, in a musical sense, than time in seconds.
Download (0.43MB)
Added: 2006-02-17 License: GPL (GNU General Public License) Price:
1347 downloads
Download (0.53MB)
Added: 2005-04-26 License: GPL (GNU General Public License) Price:
1643 downloads
Wi.Ser 0.7.1
Wi.Ser is a server-side GUI framework with a GUI builder for Swing and Web apps. more>>
WidgetServer (WiSer) is a Java/XML server-side GUI-framework which enables an application to run as either
- a monolithic application with a Swing GUI,
- a client/server application with a thin Swing client,
- or as an application with a rich Web client based on HTML and JavaScript
without any change!
The framework supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. A XML markup language helps to define an applications GUI.
Furthermore a common widget-based, object-oriented programming interface for Web and Swing GUIs is offered to the developer to control and assemble the GUI. This prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag&Drop implementation).
For Swing client/server applications the framework cares for the client/server split as well as for the client/server communication including compression and security layers. The functionality of the Swing widget set is covered widely (and sometimes enhanced) in both (Swing and Web/HTML) client channels.
The project comes with a WYSIWYG GUI-builder which is completely build on the Wi.Ser-framework technology.
Main features:
- Support for internationalisation
- Standard widgets like inputfield, combobox, radiobuttons, ...
- Enhanced widgets like treeviews, table, tabbedpanes, splitpanes, ...
- XML configuration to separate GUI definition from application code
- Unified object oriented API for all targeted clients
- Support for drag&drop operations
- GridBagLayout and absolute positioning
- Support for MDI and SDI applications
- Multiple render/templatekits to support individual CIs and multiple browsers
- Preconfigured support for IE and Mozilla
- Snapshot render widget to use individual swing renderers within the framework
- DrawPane widget to create images on the fly
- GUI events like actionevent, clickevent, keyevent, ...can be received and handled on the serverside
- Plugin mechanism to exentd the framework
- Applications are deployed either into a standard servlet container
- or alternatively into the WidgetServer runtime
- Rich functionality for input validation
- GUI builder, examples and tutorial
<<less- a monolithic application with a Swing GUI,
- a client/server application with a thin Swing client,
- or as an application with a rich Web client based on HTML and JavaScript
without any change!
The framework supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. A XML markup language helps to define an applications GUI.
Furthermore a common widget-based, object-oriented programming interface for Web and Swing GUIs is offered to the developer to control and assemble the GUI. This prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag&Drop implementation).
For Swing client/server applications the framework cares for the client/server split as well as for the client/server communication including compression and security layers. The functionality of the Swing widget set is covered widely (and sometimes enhanced) in both (Swing and Web/HTML) client channels.
The project comes with a WYSIWYG GUI-builder which is completely build on the Wi.Ser-framework technology.
Main features:
- Support for internationalisation
- Standard widgets like inputfield, combobox, radiobuttons, ...
- Enhanced widgets like treeviews, table, tabbedpanes, splitpanes, ...
- XML configuration to separate GUI definition from application code
- Unified object oriented API for all targeted clients
- Support for drag&drop operations
- GridBagLayout and absolute positioning
- Support for MDI and SDI applications
- Multiple render/templatekits to support individual CIs and multiple browsers
- Preconfigured support for IE and Mozilla
- Snapshot render widget to use individual swing renderers within the framework
- DrawPane widget to create images on the fly
- GUI events like actionevent, clickevent, keyevent, ...can be received and handled on the serverside
- Plugin mechanism to exentd the framework
- Applications are deployed either into a standard servlet container
- or alternatively into the WidgetServer runtime
- Rich functionality for input validation
- GUI builder, examples and tutorial
Download (1.72MB)
Added: 2005-06-01 License: Freeware Price:
1605 downloads
Wombat 0.7.1
Wombat is a Perl servlet container. more>>
Wombat is a servlet container for Perl. It is not an executable program itself; rather, it is a library that can be used by programs to embed a servlet container. Embedding programs must provide implementations of Connector API classes that adapt Wombat to the surrounding environment. One such connector is Apache::Wombat which embeds a Wombat servlet container within an Apache httpd built with mod_perl.
Currently no developer documentation for Wombat itself is provided beyond the contents of this document and the POD for each Wombat class.
CONTAINER CONFIGURATION
CONTAINER DIRECTORIES
Web application directories are generally located beneath a single application base directory which in turn is usually located beneath the containers home directory. Each Host configured in the container can use the same application base directory (called webapps by default) or provide its own, possibly located outside the containers home directory. As well, each Application configured in the container has the option of locating its webapp directory outside its Hosts application base directory.
A typical directory structure for Wombat embedded within Apache/mod_perl might be:
# containers home dir
/usr/local/apache
# default hostss appbase dir
/usr/local/apache/webapps
# examples apps webapp dir
/usr/local/apache/webapps/examples
# another hosts appbase dir
/home/bcm/maz.org/webapps
# another apps webapp dir
/home/bcm/maz.org/webapps/comics
CONTAINER DEPLOYMENT DESCRIPTOR
The behavior and attributes of the Wombat servlet container are controlled by a container deployment descriptor (usually named server.xml). This file is modeled after the Tomcat 4 equivalent, but it does have slight differences. A full Configuration Guide will be published; until then, the definitions included below are the only documentation:
Elements supported in server.xml (named with XPath paths, example attribute settings included inline):
Server
Represents the entire perl interpreter, into which one or more Services are deployed. Only one Server may be specified.
Server/Service
Represents a collection of one or more Connectors that share a single Engine (and therefore the web applications visible within that Engine). A display name for the Service (name="HTTP Service") may be specified. Many Services may be specified for the single Server.
Server/Service/Connector
Represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to its associated Container for processing. The name of a class that implements the Wombat::Connector interface MUST be specified (className="Apache::Wombat::Connector"), as well as a scheme (scheme="http" attribute) and any attributes needed by the implementation. A secure flag (secure="1") may also be set to indicated that the request was transported using SSL. Many Connectors may theoretically be specified for a particular Service, but at this time, the Wombat internals need some refactoring before they can support Connectors for protocols other than HTTP.
Server/Service/Engine
Represents the highest level Container associated with a set of Connectors. The Engine discriminates between virtual hosts as necessary and passes the request along to the appropriate Host. A display name for the Engine (name="Apache-Wombat") may be specified, as well as the name of a default host (defaultHost="localhost" attribute) to receive requests that are not mapped to other specifically configured Hosts. Only one Engine may be specified for a particular Service.
Server/Service/Engine/Logger
Unless overridden in a lower level Container, all log messages will be handled by this Logger. The name of a class that implements the Wombat::Logger interface MUST be specified (className="Apache::Wombat::Logger"), as well as any attributes needed by the implementation. A minimum log level (level="DEBUG") may also be specified. If no Logger is specified, logging will be disabled for the Container. Only one Logger may be specified for a particular Container.
Server/Service/Engine/Realm
Unless overridden in a lower level Container, all web applications will be subject to this security Realm. The name of a class that implements the Wombat::Realm interface MUST be specified (className="Wombat::Realm::DBIRealm"), as well as any attributes needed by the implementation. If no Realm is specified, security will be disabled for the Container. Only one Realm may be specified for a particular Container.
Note that security MUST be also enabled in a particular web applications deployment descriptor in order for the Realm to be relevant to that web application. Therefore a Realm may be configured for an entire Container but only in use for a single Application.
Server/Service/Engine/SessionManager
Unless overridden in a lower level Container, all sessions will be managed by this SessionManager. The name of a class that implements the Wombat::SessionManager interface MUST be specified (className="Wombat::SessionManager::StandardSessionManager"), as well as any attributes needed by the implementation. A maximum inactivity interval/idle out time may also be specified (maxInactiveInterval="300"). If no SessionManager element is specified, sessions will be disabled for the Container. Only one SessionManager may be specified for a particular Container.
The type of SessionManager used will depend heavily on the environment provided by the embedding program. For instance, a multiprocess Apache/mod_perl server embedding Wombat will require a SessionManager that caches sessions in shared memory, on disk or in some other location that all processes can access, whereas a multithreaded daemon embedding Wombat might use a simple memory-based SessionManager.
Server/Service/Engine/Valve
Represents a request-processing component that "wraps" around the Servlet that is ultimately responsible for processing the request. The name of a class that implements the Wombat::Valve interface MUST be specified (className="Wombat::Valve::RequestDumperValve"), as well as any attributes needed by the implementation. Many Valves may be specified for a single Container.
Valves are used to add container functionality for specific Containers, much like Filters are used to add application functionality for specific Servlets. An example of a commonly-used Valve might be a one that logs information about each request (an AccessLogValve perhaps).
Server/Service/Engine/Host
Represents a Container associated with a particular virtual host. A Host maps the request URI to a particular web application and passes the request along to the appropriate Application. The name of the host MUST be specified (name="localhost"), as well as the application base directory (appBase="webapps") which can be specified absolutely or relative to the containers home directory. Many Hosts (at least one, corresponding to the Engines default host attribute) may be specified for a single Engine.
Server/Service/Engine/Host/Alias
Represents an alternate name or names for the virtual host. For a Host named maz.org, the Alias *.maz.org might be configured to catch requests for specific hosts and subdomains in the domain. The name of the alias MUST be specified (name="*.maz.org"). Many Aliases may be specified for a particular Host.
Server/Service/Engine/Host/Logger
A Logger configured for a Host overrides any Logger configured at the Engine level.
Server/Service/Engine/Host/Realm
A Realm configured for a Host overrides any Realm configured at the Engine level.
Server/Service/Engine/Host/SessionManager
A SessionManager configured for a Host overrides any SessionManager configured at the Engine level.
Server/Service/Engine/Host/Valve
Any Valves configured for a Host add to (and execute after) any Valves configured at the Engine level.
Server/Service/Engine/Host/Application
Represents a Container associated with a particular web application. An Application inspects the request URI and passes the request along to the appropriate Servlet (as configured in the web applications deployment descriptor). The display name of the application (displayName="Examples Application") and the URI path base for the application (path="/wombat-examples") MUST be specified, as well as the webapp directory (docBase="examples") which can be specified absolutely or relative to the parent Hosts application base directory. Many Applications (at least one, corresponding to the URI path /) may be specified for a single Host.
Server/Service/Engine/Host/Application/Logger
A Logger configured for an Application overrides any Logger configured at a higher level.
Server/Service/Engine/Host/Application/Realm
A Realm configured for an Application overrides any Realm configured at a higher level.
Server/Service/Engine/Host/Application/SessionManager
A SessionManager configured for an Application overrides any SessionManager configured at a higher level.
Server/Service/Engine/Host/Application/Valve
Any Valves configured for an Application add to (and execute after) any Valves configured at a higher level.
Download (0.10MB)
Added: 2007-06-06 License: Perl Artistic License Price:
870 downloads
qooxdoo 0.7.1
qooxdoo is an advanced JavaScript-based GUI toolkit for creating rich Web application interfaces. more>>
qooxdoo is an advanced open-source javascript based toolkit. qooxdoo continues where simple HTML is not enough anymore.
qooxdoo can help you to get your rich web application interface done much easier than ever before.
<<lessqooxdoo can help you to get your rich web application interface done much easier than ever before.
Download (MB)
Added: 2007-07-09 License: LGPL (GNU Lesser General Public License) Price:
839 downloads
ftp4che 0.7.1
ftp4che is an FTP library for Java 1.4 and 5.0 that features support for implicit SSL. more>>
ftp4che is an FTP library for Java 1.4 and 5.0 that features support for implicit SSL, implicit AUTH SSL, AUTH TLS, TLS, FXP, PRET, SSCN, an event model, bandwidth control, and unlimited file sizes.
<<less Download (0.87MB)
Added: 2007-05-22 License: LGPL (GNU Lesser General Public License) Price:
888 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above 0.7.1 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
