Re: Remobjects, good in multi-threading environment?

Richard Gillingham - C4D wrote:
Hello Arthur

You might be better off switching to a messaging based store and forward architecture that is resilient in terms of comms failures.


There are some pretty extreme requirements that have to be met in our
application. We're talking about the transmission of "realtime" numerical
data here (with a -s or 2-s sample interval). The worst-case scenario that
must still work is a connection with a latency of 2 s and a bandwidth
of only 240 bytes/sec (more specifically, this is a Thrane & Thrane
Inmarsat mini-M satellite terminal). Add to this the complication that
the connection is interrupted regularly. In case of an interruption, it
is mandatory that as soon as the connection is re-established, the most
recent data is transferred first. Simultaneously, the "gaps" in the client's
database must be filled in in reversed sequence, but "current" data
must be transferred at all time because we may lag behind no more
than 5 seconds.




--
Arthur Hoornweg

(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)
.