3.3 KiB
DTP Core
The Digital Telepresence Platform is distributed. There are nodes running everywhere generating events on behalf of community members. Cores define those communities. People create and manage member accounts on one or more Core nodes. Application nodes then request to join a Core's community. If accepted, the application node can then offer it's services to that Core's members.
Application Node Connections (Core Connect)
Your Core node manages member accounts, and also serves as an identity provider to Application nodes. DTP Sites, Social, Venue, Links, etc., are all examples of Application nodes. They each implement a specific application, and they connect to the DTP Global Core to provide their services to that community.
Core-to-Core Connections (Constellation Connect)
Your Core node defines a community of people and the services they use. There can and will be many Core nodes with unique collections of members and services, and Core nodes can connect with each other to share information. When a Core connects to one or more other Core(s), they have formed a Constellation.
Open Core
An Open Core automatically accepts Core and Constellation Connect requests to join the community. The administrator is not presented with a connection request, and their approval is not required. The connection is automatic, OAuth2 credentials are immediately sent, and the connection is immediately established.
Selective Core
A Selective Core receives and stores Core and Constellation Connect requests, and delivers them to the Site Administrator for review and consideration. The administrator can approve or reject each request.
If a Core Connect request is approved, OAuth2 credentials are delivered to the Application node, and it can begin authenticating and authorizing your community members to use the service it provides, and also (optionally) start contributing events to the Community Timeline.
If a Constellation Connect request is approved, OAuth2 credentials are delivered to the Core node, and it can begin sending and receiving Constellation Timeline events.
Closed Core
A Closed Core automatically rejects and forgets all Core and Constellation Connect requests. Closed Core systems must manually add Application nodes to their Community, and other Core nodes to their Constellation.
Core Connect Procedure
Application node administrators will configure their node, then run dtp-webapp-cli.js to request a connection to a DTP Core node as follows:
node dtp-webapp-cli.js --action=core-connect host:port
The process will either automatically connect the application node (Open Core), deliver the connection request to the Core Admin (approval required), or deny the request (Closed Core). If approval is required, your node will update automatically if approved, and let you know if you've been denied.
Constellation Connect Procedure
Core node administrators will configure their Core, then run dtp-webapp-cli.js to send a Constellation Connect request to another Core node as follows:
node dtp-webapp-cli.js --action=constellation-connect host:port
The process will either automatically add your Core to the Constellation, deliver the connection request to the Core Admin (approval required), or deny the request (Closed Core). If approval is required, your Core will update automatically and join the Constellation if approved.