On 27/10/15 23:58, Alan Gauld wrote:
that enable multiple tasks to run in parallel on a single computer. Each
thread is a sub-process of the parent process.
I should add that this is a bit of a simplification because threading
varies in implementation depending on OS and language. Threads are
On 27/10/15 17:51, richard kappler wrote:
Sorry, thought it was clear. Each of the three different data
generating machines
(in the test env, the python script that sends the data with 3
different device names)
goes over a different thread so the developers tell me.
OK, You need to get the co
Sorry, thought it was clear. Each of the three different data generating
machines (in the test env, the python script that sends the data with 3
different device names) goes over a different thread so the developers tell
me. In production, those three machines are microcontrollers, not full
blown c
On 27/10/15 14:52, richard kappler wrote:
In our test environment we have simulated this by building three vm's. VM1
has a python script that sends raw data over tcp to VM2 which parses the
data and sends it over tcp to VM3 upon which we are developing our
analytics apps.
...
1. The data from
I'm having difficulty wrapping my arms around sockets and threading, not so
much from a 10,000 foot/ network perspective, but from a low level
perspective.
In our production environment we have three machines that generate data and
forward it over tcp to a computer that stores the data, parses it
