SNComponents

Topics

• Certificates and contacts
• Chat - Makan
• Write you own component

SN2 is a showcase, test platform and playground to implement new application components. Here are some SN2 component rules:

• No circular dependencies. Components can use others but vice-versa. There is a component hierarchy. Components with no further dependencies are called root compoments
• Components implement the ASAPApplicationComponent interface.
• There is an example that shows how it can be integrated with SharkNetApp.
• Each Component uses its own ASAPEngine and can be distinguished from other by its format.

Root components

Certificates and contacts

This components manages contacts, their names and certificates. It provides public keys and offers methods to manage the local private/public key pair. It includes an Android Key Storage.

It uses ASAP to spread certificates within a peer group. You do not have to deal with user management and anything about a public key infrastructure (PKI). This component does not offer methods for ASAP encryption and digital signing. It provides methods to get public keys and the local private key, though.

Have a look at the ASAP Certificate Component Wiki for concepts and some details. (The considerations about identity assurance are quite unique and special to this kind of decentralized networks.)

Contact and certificate management is implemented in package net.sharksystem.persons. The PersonsStorage facade gives access to all relevant methods in this component.

Dependent components

Makan

Write you own component