-
It is sometimes useful to know the remote Engine implementation. For example, when using the [supported Node.js implementation](https://github.com/southlogics/node-jstp) the Protocol Header may look l…
-
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) connection…
-
Which are the stages involved in processing?
- Validating
- Forwarding/Triggering
- Binding/Releasing (if it is a Subscription Dispatch!)
Expand
-
The idea is to have only one argument rather than the three currenctly used for the callbacks.
JSTPMessage.
JSTPMessage will contain:
- `engine`: The JSTPEngine
- `answer`: if this is an ANSWER Disp…
-
Is this the place for an implementation recommendation?
-
Auto-rebinding: Engine-level reconnection attempts to named hosts (servers) where all remotely bounded endpoints are attempted to be re bound in time.
This is not currently mandatory in the specifica…
-
Like a `JSTPAnswer` or `JSTPAnswerDispatch`. Not significant right now since current implementations sensibly use plain JSON. I'll just drop the question.
-
Tip: try to replace the event for `on("close")`
-
Subscribers should be distinguished as both Emitters and Channels. The difference being that Channels are network or virtual host connections and arbitrary Dispatches sent back using those existing co…
-
> Moved from the [Ruby JSTP implementation](https://github.com/Fetcher/ruby-jstp)
This refers to the protocol rather than the library. The proposal is to, alike HTTP, delegate the Host as a different…