Add Chronicle-Websocket-Jetty integration for Chronicle Engine.
peter-lawrey opened this issue · 2 comments
peter-lawrey commented
Support access to queues and maps via web sockets, with a sample program in Java Websockets and JavaScript.
This will help demonstrate Engine as an API Gateway http://microservices.io/patterns/apigateway.html
e.g.
- attach to an asset via URL
- publish messages and enable subscriptions via JSON commands.
Later I would like to be able to bind to an actor/value in a map or queue and issue method calls.
RobAustin commented
@peter-lawrey is this something that you still want done, especially now that we are moving to chronicle-services. I don't think this is a priority any more, so will move it to "wont fix" and close it. Please re-open if you disagree.
peter-lawrey commented
I think this should be integrated with Chronicle Services when we have use
case to do so.
ᐧ
…On 2 January 2018 at 15:31, Rob Austin ***@***.***> wrote:
Closed #13 <#13>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBU8WVRyctKOGKo6Eu00Y7hSmI8LI7nks5tGkvPgaJpZM4JThy0>
.