Amun

Building a more federated and programmable web

Location: Amun / About /

About

This page should explain more detailed how Amun works and how open technologies are implemented.


RESTful API OAuth protected

Amun communication flow

Figure 1. API communication flow

Figure 1 shows an example how you can access the RESTful API. The API can provide the data by default in JSON and XML. For many services it is also a ATOM and RSS feed available. The API is designed after the OpenSocial Core API specification.

Because Amun is managed via an RESTful API it is not limited to be a content managment system for websites it can also be used for desktop applications or any other application wich needs to store and retrieve data from a server (in the cloud).

As Figure 1 shows OAuth authentication is only necessary if you connect from a different host system. Within Amun you can access the API also via javascript. This has the advantage that all web forms in Amun use also the RESTful API to insert, update or delete records. Please see the backend section for a list of available backend systems.


Distributed Social Network

Amun communication flow

Figure 2. Distributed social network

It is possible to connect multiple Amun instances into a network. This has the advantage that users only need to register one account. On other websites in the network they can use their existing account to login. The authentication is made with WebFinger and OpenID. Figure 2 shows through wich technologies websites are connected together.

Also within the network you can add every user as friend. The exchange of activities between website will be done via PSHB but this part still needs some work and testing.


Active messaging

Amun supports active messaging via stomp. That means it is possible to notify a message broker everytime a record is inserted, updated or deleted from a table. That has the advantage that time consuming tasks can be executed by a script wich is called from the broker.

by last modified on