Re: User space

[Raul A Jager <raul@xxxxxxxxxx>]

In all the samples I have seen, the user space was used to hold the 
output from an API.

In my case, I have several user entering transacctions, and I want to 
know who was the one that finsh the last transaction up to now, and 
provide that info to everybody else.  someting like:
____________________________________

Last completed transaction by:  USER7
____________________________________

Refresh may show somebody else, or the same user.
If two users complete a transaction at the same time, any one of them 
should appear.

It is almost like a STACK, where I can only see the TOP.  The difference 
is I only care about the TOP, and I want to discard the rest.
A field from the user space as output on the screen does the trick.  The 
time on screen shows when that was valid, refresh will update the time 
and the user.  It is working the way I want it, it was easy to program.

I'm still curious to know if there is a better way to do it.

Raul
____________________________________________________________________________________________
Scott Klement wrote:

> IMHO, the problem here is that you're trying to use user spaces for
> interprocess communications, and that's not what they're designed for.
>
> Either use data queues to synchronize access to the user space, or just
> use data queues to pass the data...
>
>
> On Fri, 13 Feb 2004, Raul A Jager wrote:
>  
>
> > ...for those of us who are repelled by the idea of delving into
> > mi to lock a user space however we do utilize user spaces where beneficial,
> > wouldn't we derive the same anti-lock capabilities using the ALCOBJ
> > command..?
>