Re: Hmmmm.....$1 Billion

On Thu, 3 Mar 2005 22:04:01 -0600 (Central Standard Time), Booth
Martin <booth@xxxxxxxxxxxx> wrote:
> I will now show my ignorance and then be quiet.
> 
> A message loop?  Like... a cycle?

yeah, but the rpg cycle is a do loop.   a message loop that receives
from a data queue is different from a logic loop that loops until
*inlr = '1'.

-Steve

> 
> ---------------------------------
> Booth Martin
> http://www.martinvt.com
> ---------------------------------
> -------Original Message-------
> 
> From: Midrange Systems Technical Discussion
> Date: 03/03/05 21:48:14
> To: Midrange Systems Technical Discussion
> Subject: Re: Hmmmm.....$1 Billion
> 
> On Thu, 03 Mar 2005 20:25:28 -0600, Vernon Hamberg <vhamberg@xxxxxxxxxxx>
> wrote:
> > We must be talking different things here - VB for the longest time did not
> > have thread capability, yet was considered event-driven. So you must mean
> > something different.
> 
> for event driven programming you need a message loop. Every windows
> program has, at its heart, a message loop.  The Windows OS feeds
> events like a keystroke, mouse move, a command to close the window to
> the windows message queue.
> 
> on the 400 you dont have that default message loop.  If you want to
> use an event model for your interactive job you need threads to
> implement the whole thing.  The main thread would receive from the
> message ( data ) queue, processing the events.   Other threads would
> feed events like "the user has pressed the enter key", a socket
> receive has returned some data,  a physical file trigger has fired
> because a record has been added to a file.
> 
> All of this is just a big example because display data managment and,
> I guess 5250,  does not handle change of direction very well. Once the
> display is waiting for the enter key to be pressed, the device is not
> available to have a new screen written to it.
> 
> Whether this is all true, I am not sure.  I am just using the topic as
> an example of what could be done with threads and other improvements
> to the system.
> 
> -Steve
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> .
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>