(Resending the e-mail, Sourceforge might have dropped it as it has not shown up
so far. ---rony)
-------- Forwarded Message --------
Subject: Re: [Oorexx-devel] addresswith: timing of monitor data
dispatching ...
Date: Sun, 29 Apr 2018 15:46:50 +0200
From: Rony G. Flatscher <rony.flatsc...@wu.ac.at>
To: oorexx-devel@lists.sourceforge.net
On 28.04.2018 18:53, Rick McGuire wrote:
> What part of "this is not real time" are you not understanding. All of the
> data is buffered, so
> the first thing that happens is all of the input data is read and buffered
> and then written to the
> pipe. The output data is similarly buffered and not written out until the
> command completes.
Was not aware that the command gets blocked until all of the input was read in
full (at least in the
monitor case).
What about use-cases like having an ooRexx program running for a couple of
hours or even for 24
hours / 7 days a week, feeding/pumping constantly information via a Rexx input
monitor to the
command, e.g. data pulled/retrieved from sensors in the abstract sense (e.g.
from true sensors to
applications that may constantly supply quotes from stock-exchanges and the
like)?
Couldn't the producer-consumer-pattern be applied here to allow close to
"real-time" usage of the
address-with redirected input, output and error streams, e.g.
<https://msdn.microsoft.com/en-us/library/dd728068.aspx>,
<https://gist.github.com/iikuy/8115191>,
<https://en.wikipedia.org/wiki/Producer%E2%80%93consumer_problem>?
Also, it seems that currently the monitors are somehow aligned to the stream
pattern by getting
LINEIN and LINEOUT messages sent to them which somehow implies that only text
data could be
processed. If it was possible to send the monitors the messages "INPUT",
"OUTPUT", "ERROR",
depending upon whether being employed as input monitors, output monitors or
error monitors, then
this would also allow for implementing all three functions as methods in a
single class (and a
single monitor for all three streams). The message names would be semantically
neutral and not imply
that only text data gets processed.
> Also, you are running with the most recent revision? I fixed a couple of
> problems with hangs on
> the streams this week.
Yes, I usually watch the svn commits and when seeing updates to your
"addresswith" (or for that
matter your "reference") sandboxes, I create a new 64-bit version of ooRexx for
Windows and place
them to my DropBox sandbox directory
<https://www.dropbox.com/sh/olh1mqfwb4brp7r/AABI1X-Le9zDCJ0gyfvMdKB8a?dl=0> to
allow others
interested in testing/exploring to download and install it. The installation
packages also carry the
svn revision number and the date when created.
---rony
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
