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.
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:
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?