Atomojo 2.0 V2 Server

A new server design is being developed with the following goals:

• merging the "server" and the "web server" via Restlet mechanism so applications and APP server components can run side-by-side,
• using a single XML configuration for the APP server so that the server isn't a closed system,
• removal of atom feeds configuration (to much self-recursion and too complicated),
• reliance on an XQuery-enabled database for feed storage,
• use of XProc for APP implementation.

A release is available for download. See the V2 Server page for more information.

Overview

This project contains both an Atom Publishing Protocol (APP) server and client. While both are intended to be used together, as they implement a standard protocol, they can be used with other APP-enable applications.

News Archive

Atomojo Firefox Extension

The client is a Firefox plugin that contains an XPCOM component for interacting with the Atom Publishing Protocol (APP).

You can install it from the addon page or download from this site. If you download it from this site, just drag the XPI file onto an open firefox window.

Documents

• Using Atomic with Blogspot.

Atomojo Server

The Atomojo server provides a uniform way to store multiple feeds and manipulate them with the Atom Publishing Protocol (APP). Feeds are organized hierarchically and indexed by their categorization. It provides both metadata feeds for getting context information about feeds as well as pulling a feed for each categorization stored in the database.

The server runs on top of a restlet.org engine and uses a rest-style URI architecture for its feeds. Feed are organized hierarchically just like a file system using a plug-in based storage system that current supports files and an XML database called eXist.

In addition to querie facilities provided by the storage (e.g. XQuery for eXist), there is a metadata index that is stored in an embedded Derby database. This index stores information about what feeds contain what entries as well as information about categorization.

Once the server is started, you can get the service introspection document by a GET on the server root. All feeds are available under the /R/ URI hierarchy, terms are available under /T/, and metadata is available under /M/.

Documents

• A development Roadmap for future directions.
• The Administration Guide for the server.
• The Users Guide for the server.
• The APP Extensions implemented by the server.
• Using XQuery with the server.
• The Atomojo Term Ontology describes the entry categorization used by the server.
• A specification of the pull synchronization process.
• A specification of the push synchronization process.

Getting Started

Just download the jar-file installer and following the instructions in the Administration Guide for installing and running the server. Once you've done that, you can immediately start working with the server.

When the server first starts for the first time, it creates the database. A administrator user is created with the username and password of 'admin'.

The database is initially empty. You need to at least create the root feed. Given the server bound to the local host, you just need to post a feed to the root path:

POST /R/ Content-Type: application/atom+xml ... <feed xmlns='http://www.w3.org/2005/Atom'> <title>Root</title> </feed>

You can use the poster addon to do this if you wish.

In fact, you can create your feeds at any point in the hierarchy. If you want to start with a feed at /x/y/z, you'd just post your starter feed document to that path.

Once you've got the server running, you can get the introspection document from the root of the server (e.g. https://localhost:8080). There is a single workspace that will be empty until you create at least one collection.

Auth Service

The auth service provides an implementation of the auth protocol. The service itself is self contained and allows you to store multiple "realms" of authentication. This service is capable of supporting multiple atomojo servers.

Documents

• A development roadmap for future directions.
• The Administration Guide for the server.
• The Authentication Protocol.

Getting Started

Just download the jar-file installer and following the instructions in the Administration Guide for installing and running the server. Once you've done that, you can immediately start working with the server.

When the server first starts for the first time, it creates the database. A administrator user is created with the username and password of 'admin'.