search

jstp / jstp-rfc

JSON Transfer Protocol RFC
0 stars 0 forks source link

Token Header extensions #26

Closed xaviervia closed 11 years ago

xaviervia commented 11 years ago

The Token Header is nowadays mainly the placeholder for the Transaction ID. However, in the coming Authorization module for JSTP, the Token Header will be used to identify incoming (client) connections to the Authorizer, so an array is not extensible enough. It stopped scaling.

The next proposed extension will be to use a hash rather than an array. And it will feature standard sub-headers.

Header sample:

"token": {
  "transaction":"<the-transaction-id>",
  "client":["<emitter-token>","<first-proxy-client-token>","<second-proxy-client-token>"]
}

Following this logic, each JSTP Engine should append its client token (from the client-token table) to the token.client header prior to Triggering.

A pending decision: should Local Emitters have their own token?

xaviervia commented 11 years ago

Nope. The client part should be the Referer.

This gets delayed.