Free server side software for linux

eXtensible Server Side Markup Language is based on XML and Struts technologies, and allows for an easy and streamlined creation of various technical and business rules with further implementation as Web services and interfaces.

It features the ability to define XML structures and ties such to actual Java code, conditional and flow processing logic, variable definition by value and reference, and logging both at class and custom component level.

WidgetServer is a component based 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 and without loss of functionality!
WidgetServer gives you the choice if you develop a GUI either using
- HTML markup,
- a Java API like Swing,
- or XML markup.
XML markup helps to define an applications GUI fully separated from java code, Java code is useful for dynamic creation and modification during application runtime, while HTML markup is the best choice for typical web applications.
WidgetServer provides a unified component-based, object-oriented programming interface for Web and Swing GUIs to control and modify the GUI and to process events. The framework prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag and 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. Web applications are fully AJAX enabled while this feature remains fully configurable.
The framework also supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. 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.
Enhancements:
- This version fixes some bugs in the JavaScript library.
- The Component-Set example is more interactive now.
- A new component similar to JSpinner has been added.
- A new package to create wizard based applications by declaration was added.
- Some enhanced error messages help to detect XML configuration errors now.

SILC Server provides system administrators ability to easily and quickly set up new SILC networks. SILC Server is full implementation of server side of the SILC protocol.
SILC Server is ideal for small offices and organizations to set up secure conferencing network in LAN. SILC Server is compact and fast, and scales easily to Internet usage as well.
SILC Server provides full featured implementation of server side of the SILC protocol. The SILC Server is intended for system administrators who would like to set up either own SILC router or SILC server.
SILC Server is ideal for small offices and organizations to set up secure conferencing network in the local area network (LAN). SILC Server project is also suitable for Internet usage as it scales well, is compact and fast.
SILC Server can act either as SILC router or SILC server. It is also able to act as Backup router and take the responsibilities of the primary router if it becomes unresponsive. If your network has only one server then SILC Server acts by default as router server. Small LAN networks manage fine with only one SILC Server so it is very easy and fast to set up.
The difference of router server and normal SILC server is that router server handles most of the message routing and also keeps the global network state up to date. Normal SILC server on the other hand handles only local users and message routing to them. This arrangement makes the SILC network fast and scalable. SILC Server is easy to configure to act either as normal server or router server.
Whats New in 1.0.4 Stable Release:
- This release fixes a small problem with parsing the 1.3 protocol version string correctly.
- Clients that conform to the 1.3 protocol will not be able to connect to a SILC server that isnt running this version.
Whats New in 1.1 Beta 1 Development Release:
- Support for the new SILC Toolkit was added.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

Fedora Directory Server is a full-featured LDAPv3 compliant server.

In addition to the standard LDAPv3 operations, Fedora Directory Server supports multi-master replication, fully online configuration and administration, chaining, virtual attributes, access control directives in the data, Virtual List View, server-side sorting, SASL, TLS/SSL, and many other features.

The transactional Berkeley DB 4.2 is used as its data store and a full plug-in API allows developers to extend the the functionality of the server in many ways, and many of the core features of the server are already implemented using this API.

The server is very mature, having started out as Netscape Directory Server.

gregaire project consists of a server-side RSS aggregator.
gregaire is a flexible web based RSS -aggregator written in PHP 5.
It uses a database like MySQL or SQLite (http://www.sqlite.org/) to store its data. The user interface is written in standards compliant XHTML, CSS and Javascript (DOM).
Thanks to SQLite you should be able to install gregaire on any webspace on earth, supposed the webserver runs with PHP5.
gregaire is open source software released under the GNU LGPL license.
Main features:
- Be able to check your news from any device connected to the web
- Have the comfort of using the same application anywhere
- Avoid reading news multiple times
- Get back to already flagged and categorized items
- Make use of multi-user and collaborative features
- Let the server gather the news for you automatically

SecureJSH project enables server side applications written in the Java programming language to provide secure shell access to their administrators, users, developers and service clients, where verbatim syntax of the latest Java programming language can be used - interactively.
SecureJSH needs JDK 6.0 (or later) or JRE 6.0 (or later) with JAVAC on classpath to function.
Security:
SecureJSH implements RFC-4251 SSH 2.0 protocol at the server side, with support of publickey authentication, which is more secure and convenient (no need to enter password every time).
Interactive Execution:
You must first compile traditional Java source code to bytecode before
executing them. But with SecureJSH, the compilation is done transparently so
you just type in arbitrary length of Java statements, then see them get
executed immediately, in context. Context objects are all well kept across
executions, this way you interactively control a live Java application with
the programming language it was writen in.
Verbatim Java Syntax:
Unlike other Java shell supporting tools, SecureJSH leverages JSR-199 Java
compiler API to dynamically compile interactive Java statements. This means you use the EXACTLY same syntax with whatever your applications are writen in, up to the latest Java Language Specification. You can copy & paste code between SecureJSH terminal and your Java project source without problem.
Smart Command Recognization, UNIX Shell Style
Unlike JSR-223 scripting support for the Java language, with which you must
enter the full source of a Java class to execute, SecureJSH is much smarter and
humanized, it prompts you for multi-line input when youve entered incomplete
Java statements, and wraps the statements inside a predefined class structure
for execution. It is a REAL shell.
Non-Interference, Minimum Resource Consumption
SecureJSH has no static resource has to be stored JVM wide, and consume very small amount of resources per instance (with NIO based implementation, all SSH traffics are handled by a single thread). You can run as many shell servers as you wish inside a single JVM, including JVMs of Java application servers.
Commercial Friendly License
SecureJSH is released under a BSD style license. Please read the included
LICENCE.txt for SJSH and third-party license terms.
Enhancements:
- The Java completion algorithm was refined and is more accurate and to the point.
- Rarely used methods like Object.wait() and Object.notify() are filtered out.
- Completion for built-in command options was added - press Tab to complete a command, then Tab again to prompt for common options.
- This works fine with dynamic options (like unimport java.awt.*
- can be entered by uni-[Tab]-j-[Tab], when such an import is in the list).
- The field definition command now takes a type name before a field name, to match the Java variable definition style.

JavaScript Browser Sniffer is a browser identifier written in JavaScript (EcmaScript) and released under the LGPL license. It can tell your browser name, version and operating system you (the visitor) are using (its like phpsniff, but in JavaScript)
Main features:
- Microsoft Internet Explorer (should work with any version)
- Netscape 4.x, 6.x and 7.x
- Mozilla Seamonkey, Galeon, Firebird, Phoenix, Epiphany, K-Meleon, Camino and Chimera (should work with any version)
- Opera (should work with any version)
- Konqueror (should work with any version)
- Nautilus (version number is not available yet)
- Safari (should work with any version)
- Omniweb (should work with any version))
- Links (should work with any version)
- ELinks (should work with any version)
- PowerMarks (should work with any version)
- Crazy Browser (should work with any version)
- MyIE2 (should work with any version)
- Java (should work with any version)
- iCab (should work with any version)
- NetFront (should work with any version)
- Avant Browser (should work with any version)
- MSN Explorer (should work with any version)
- w3m (should work with any version) (please note that w3m only supports JavaScript on the client-side if using w3m-js)
- Netcaptor (should work with any version)
- Dillo (should work with any version) (only server-side)
- Lynx (should work with any version) (only server-side)