-
> Moved from [JSTP Ruby Gem](https://github.com/Fetcher/ruby-jstp)
Add subscription feature for event-driven architectures.
An event is triggered for Subscriptors to received whenever an inbound dis…
-
While JSTP packages are described as Dispatches because there is no protocol-level request-response specification, the request and response idioms are useful to describe such circumstances such as tho…
-
There should exist an specific Dispatch Morphology (like the BIND Morphology and the Regular Morphology) for exceptions. The rationale is:
- Some Dispatch emitters may expect an exceptional response i…
-
There are two strategies with which engines may be instructed to process BIND and RELEASE Dispatches:
- Strict: The caller is responsable for maintaining consistency in the BIND and RELEASE calls. Und…
-
This refers to the protocol rather than the library. The proposal is to, alike HTTP, delegate the Host as a differentiated header in the JSTP Dispatch rather than the first item in the Resource. The r…
-
Add subscription feature for event-driven architectures.
A suggestion for this type of architecture can be found here https://github.com/Fetcher/jstp/issues/4#issuecomment-13237310
-
The JSTP Engine should redirect automatically Dispatches that select a different hostname of that of self.
This functionality should be switchable on and off, and should be on by default.
Since 'lo…
-
The JSTP::Engine should be able to hook functionality on new client and closed client. JSTP creates a UUID for each new client: the client representation and that UUID token should be passed to the ho…
-
# open and #close methods in the JSTP::Engine should apply to TCP Sockets as well. But later, since now every client gets closed after completing a Dispatch.
-
The relevant question is, which type of connection should be supported, stateless of persistent connections?
An issue with stateless-only is that renders impossible connection reutilization, but a bi…