Re: Hmmmm.....$1 Billion

[Don <dr2@xxxxxxxxxxxx>]

well....yes and no.  It's kinduva complex way of constantly polling a
set of devices to see if anything has changed in their status or buffers
and then reacting accordingly to it.

Now, as I recall that's hitting an area refered to as interupt driven vs
queue driven processes...  Don't go there every day and I'm sure there's a
few folks out there more current than I am on this...

But then, it's almost midnight and I've been without coffee for at least
12 hrs....so, anything's possible.

Don in DC

--------------------

On Thu, 3 Mar 2005, Booth Martin wrote:

> I will now show my ignorance and then be quiet.
>
> A message loop?  Like... a cycle?
>
> ---------------------------------
> 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.
>