In the jsonrpc era, I can't think, offhand, about a good reason to
keep these two connections.
Liron - any insight?
On Tue, Jan 24, 2017 at 6:18 PM, Roy Golan wrote:
> +storage ping
>
> On 17 January 2017 at 12:19, Piotr Kliczewski
> wrote:
>>
>> It should be enough to subscribe to irs specific
+storage ping
On 17 January 2017 at 12:19, Piotr Kliczewski
wrote:
> It should be enough to subscribe to irs specific queues. Instead of
> creating new client we can rely on status of a subscription.
>
> On Tue, Jan 17, 2017 at 10:54 AM, Roy Golan wrote:
> > For each SPM host the engine creates
It should be enough to subscribe to irs specific queues. Instead of
creating new client we can rely on status of a subscription.
On Tue, Jan 17, 2017 at 10:54 AM, Roy Golan wrote:
> For each SPM host the engine creates a different stomp connection (See
> JsonRpcIIrsServer.java) . This also means
For each SPM host the engine creates a different stomp connection (See
JsonRpcIIrsServer.java) . This also means another client connection to
maintain on the SPM machine.
What is the reason we still have it and what does it guarantee? Please add
any info here prior to opening a bug to remove it fo
