nuXleus Application & Messaging Appliance
Latest Release: http://www.rpath.org/rbuilder/project/nuxleus/releases
Project Description
The nuXleus Project is comprised of two primary node-types: A client and a server.
Client
As it relates to the client, the Nuxleus Project has the specific intent to become a User-Centric/Specific Application and XML messaging virtualization-based appliance in which a primary, user-specific/centric host machine can use as a secured proxy for all web-based communications.
PLEASE NOTE: Please keep in mind this project is not intended nor designed as a stand alone solution, or in other words, this project has no intention of ever becoming the primary operating system on any given host. Instead we have the specific intent to develop integrated solutions to work with existing operating system installs, acting as a virtual and secure gateway to the web in which a host OS can then use as a proxy to communicate with other nodes, and in doing so minimizing the overall exposure to the outside world.
Our goal, in fact, is to reduce this exposure to ZERO, using Nuxleus as the primary and only point of contact to the outside web, while acting as our personal, online presence hosting provider. Using this synopsis, Nuxleus can then provide a safe and secured environment to provide extended web-based services built around the overall vision of the Semantic Web*, ensuring that our personal host OS never has the need to risk that which could lead to any type of malware, virus, worm, or other form of threat from the outside world by limiting ALL communications to first pass through the Nuxleus interface, to then be examined for potential threats, checked for proper security credentials, passing the result to the host system if, and only if, ALL security processes in place have given each specific message the green light to be passed through a single secured port on the host machine.
Server
TODO:
Technology Overview
The Nuxleus Project platform is built on top of a system of simple XML messages that are passed from one process to the next until the original intent of any particular request has either completed successfully or failed completely. The core of this system relies upon the use of a logging mechanism for each sub-process (micro-process) within any given transaction process (macro-process) that insures that once the delivery of any particular message to any particular micro-process has completed successfully, it can forget about everything and move on to handling the next request that comes its direction. In other words, as a process is taking place, the start time, the end time, the parameter names and related values, and the result of the micro-process are sent to a queue server who's only task is to handle the logging of each completed request in such a way that if something goes wrong, the logging system can be queried, the entire process up until the point of failure reconstructed and returned, and the result of that query processed, analyzed, if at all possible fixed by the system itself, and if not, a blip notification sent to a particular URI for further review by a human.
System Architecture
There are five primary pieces of the Nuxleus Project System Architecture,
Latest Project News
The following is outdated and in desperate need of an update.
Monday, January 1st, 2007
The first official preview release is now available. For now, please visit http://www.oreillynet.com/xml/blog/2007/01/annnuxleus_the_nuxleus_project.html where you will find links to the various available downloads as well as an overview of what is include in this release.
Project Links :: WebFeed:Latest Project Info : Project Home Page : Base Camp aka "Project Development Home Page" : Site Index
