Re: [MiNT] AES in kernel (was: XaAES / GEM memory issues)

[Henk Robbers <h.robbers@chello.nl>]

Jo-Even.Skarstein@vital.no wrote:
> 
> > -----Original Message-----
> > From: Guido.Flohr@t-online.de [SMTP:Guido.Flohr@t-online.de]
> > Sent: Tuesday, January 09, 2001 3:24 AM
> > To:   MiNT mailing list
> > Subject:      Re: [MiNT] AES in kernel (was: XaAES / GEM memory issues)
> >
> > advanced applications could benefit from the new design:  Take for example
> > a graphical web browser that wants to select i/o from a handful of sockets
> > and still wants to poll the mouse, keyboard and the AES message
> > queue.  Currently you need two event queues for that: One for the AES
> > (evnt_multi) and one for i/o (poll/select).  If the AES provided devices
> > for all that, it could be done all in one loop (and it is also a very
> > natural view to treat i/o on a file descriptor and a mouse movement
> >
> Isn't this one of the key ideas behind XaAES? IIRC you can receive all
> events through the event-pipe, which means that you can use one single
> select() to wait for both AES events and any other file descriptor (such as
> sockets).
> 

Exactly. This approach makes XaAES extrememly multitasking friendly.
The select includes the mouse and keyboard events. This makes its internal
architecture uncomplicated and easy to follow.

> Btw. doesn't this mean that we need a new select() in MiNT? It's currently
> restricted to 32 file descriptors, right?

Definetely.:-)

-- 
Groeten; Regards.
Henk Robbers.    mailto:h.robbers@chello.nl
                   http://members.ams.chello.nl/h.robbers/Home.html
A free multitasking GEM for MiNT: XaAES (heavily under construction);
Interactive disassembler: TT-Digger;  Experimental text editor: AHCX;