zmq sockets client checked before creating them

This commit is contained in:
2020-03-11 11:09:41 +01:00
parent 93f8e8ecb3
commit 7a6797b23e
2 changed files with 10 additions and 0 deletions

View File

@ -25,6 +25,7 @@ This document describes the differences between 4.2.0 and 4.1.1 releases.
- (Receiver) performance (memory allocation and alignment, file buffering) - (Receiver) performance (memory allocation and alignment, file buffering)
- (Package) Removed warnings including memory overlap copy - (Package) Removed warnings including memory overlap copy
- (Users) Added setflippeddatax to users class - (Users) Added setflippeddatax to users class
- (zmq) Client zmq threads created each time client data streaming enabled
Compared to 4.1.1, Compared to 4.1.1,
- no firmware update required for this release - no firmware update required for this release
@ -76,6 +77,12 @@ This document describes the differences between 4.2.0 and 4.1.1 releases.
------- -------
1. Many warnings have been fixed, including those with overlapping 1. Many warnings have been fixed, including those with overlapping
memory copies for source and destination. memory copies for source and destination.
Client
------
1. Each time client data streaming was enabled to receive, it
creates zmq sockets without checking if they were already created.
This is fixed now.

View File

@ -5159,6 +5159,9 @@ int multiSlsDetector::createReceivingDataSockets(const bool destroy) {
cout << "Destroyed Receiving Data Socket(s)" << endl; cout << "Destroyed Receiving Data Socket(s)" << endl;
return OK; return OK;
} }
if (client_downstream) {
return OK;
}
cprintf(MAGENTA, "Going to create data sockets\n"); cprintf(MAGENTA, "Going to create data sockets\n");