basic internims framework

cni / nims

Legacy version of NIMS. All new development at @scitran

14 stars 12 forks source link

basic internims framework #58

Closed gsfr closed 10 years ago

gsfr commented 11 years ago

main components:

instance registry with internims central (currently on GAE)
peer retrieval from internims central
peer to peer communication

Communication for all components has to be secure and authenticated (probably using CRAM).

kevlarkevin commented 11 years ago

accidentally closed this issue. should remain open until all framework components are completed.

working components:

instance registry with internims central (on GAE)
peer retrieval from internims central
CRAM

remaining components:

peer to peer communication

gsfr commented 11 years ago

The http User-Agent header looks like a possible way of identifying server-to-server API requests. For example, User-Agent: NIMS Instance stanford-cni

kevlarkevin commented 10 years ago

basic framework works.

instance registry with internims central (on GAE).
peer retrieval from internims central. peer retrieval does not include own instance.
peer to peer communication. P2P requests are identified using http User-Agent header.
peer registration/expiration history is logged to datastore.

communication for all components is secure and authenticated with CRAM.