Home

Setup

You are familar with programming an ASAP peer? Very good. Let's talk about components.

But before we start:: Add two additional libraries to your project: SharkPeer and ASAPHub.

Shark Component Model

Your apps will most probably be very helpful in other applications. Developers do not like to read lengthy documents, though. We need a slim mutual understanding how to integrate code from others to your project or vice versa.

That is what we call Shark – Shared Knowledge. It is a concept: Implement decentralized apps (based on ASAP) and make them work together.

Just a few issues needs to be tackled by a component model:

1. Different applications must not use the same format. ASAP applications will exchange different data and provide different features. ASAP applications make themself distinguishable by defining an application name (e.g. "application/x-yourAppName"). We need to know those formats descriptions when we integrate another component.

2. Initialization / Dependencies Some components need to be initialized before usage. Components use each other. We need a way to initialize and connect components during system start up.

3. Peer startup In the end, there is still just a single ASAP peer sending an receiving messages. This peer must be started after the initialization process.

Continue with how to describe your component.