Free gwebcache servers software for linux

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.

Tigase Server project is a lightweight and scalable Jabber/XMPP server. No third party libraries are needed. For services with very high load and a huge number of users, it can be deployed on as many machines as needed.
Enhancements:
- This release corrects and improves the packet filter, adds a startup script for Mandriva Linux, and fixes a problem with stream initialization on very fast machines.
- The IOService class is now synchronized.
- There are many performance improvements, and processing packets from/to remote servers has been added.

Streamnik Server project is an IPTV server based on the open codecs Ogg/Vorbis and Ogg/Theora. It can stream a number of different channels and is optimized to run on leased (virtual) servers. The program schedule is defined by an SQL database table and can be changed at runtime.

C++ Server Pages is a partial Java server pages and servlet implementation in C++. C++ Server Pages is written as Apache 2.0 modules, with the focus on performance.

Anemon Dhcp Servers goal is to create an implementation of the DHCP protocol under GPL and a lot of stuff around to facilitate network management.
The python sqlobject modules gives anemon the ability to use many database as backend (mysql, postgresql, mssql, sqllite, sybase, etc..)
The project is subdivised (at the moment) in 4 components :
- The Anemon Dhcp Server is a Python/SQL implementation of the DHCP server protocol
- The Anemon Web Center is a web management interface to Anemon Dhcp Server and MyDNS
- The Anemon Dhcp Client will be a Python implementation of the DHCP client protocol
- The Anemon Dhcp relay will be a Python implementation of the DHCP relay protocol

The Cyrus IMAP server is generally intended to be run on sealed systems, where normal users are not permitted to log in.

Electronic mail is a major infrastructure service of almost all organizations. At Carnegie Mellon the use of electronic mail has overshadowed the use of all other distributed services since the early 1990s. It is a core part of the business process of most departments. The universal availability of the Andrew Mail and Bulletin Board System (AMS) has helped a great deal to create this situation. Departments without AMS have run their own mail systems and see heavy use, as well. With the end of the lifetime of the AMS in sight, Project Cyrus began to build a new campus mail system.

The Cyrus Electronic Mail Project is continuing to build a highly scalable enterprise mail system designed for use in a small to large enterprise environments using standards based technologies. The Cyrus technologies will scale from independent use in small departments to a system centrally managed in a large enterprise.

Visitors to this site may want to also view The Cyrus Wiki, which is likely to be updated more frequently.

This document gives an overview of the Cyrus IMAP server. The Cyrus IMAP (Internet Message Access Protocol) server provides access to personal mail and system-wide bulletin boards through the IMAP protocol. The Cyrus IMAP server is a scalable enterprise mail system designed for use from small to large enterprise environments using standards-based technologies.

A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through software that is using the IMAP, POP3, or KPOP protocols.

The private mailbox database design gives the server large advantages in efficiency, scalability, and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies.

XBashServ is program to help run and manage computer game servers and other general network servers.

It is designed to be easy to use so that you spend less time setting up the server and so that more players have more time to enjoy gaming on it.

LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. It takes care with the number of clients using the connection and decides upon this number whether the connection should be up or down.
The clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)