WaitSelect() with Reaction

[jahc]

Heres a message I just posted to the amiga-c mailing list.. hopefully someone here might be able to help me, if the people on the amiga-c ml arent able to...

> On Mon, 24 Mar 2003, jahc2 wrote:
>
> > I'm having trouble using multiple tasks/processes and msgports,
so
> > now I'm looking into just using one task to handle every thing.
I'm
> > making an internet program with a MUI GUI. How can I make my
program
> > wait until there's information waiting at my socket? I'm thinking
> > WaitSelect() could possibly do the job? I want to wait for
internet
> > activity AND gui stuff at the same time, if thats possible.
>
> Correct, just use WaitSelect() instead of Wait() there... Also
remember
> use sockets in the non-blocking mode. Otherwise your UI gets stuck
very
> easily when sending/receiving data.

I'm using a Reaction GUI in my program now, and it wont process GUI  stuff until data arrives at my socket..

GetAttr(WINDOW_SigMask, window_obj, &signal);

WaitSelect(STDIN, &readfds, NULL, NULL, &tv, &signal);

I dont think "signal" is being signalled when I try to use my GUI. Does anyone here have any Reaction experience?

[PiR]

Hi

It was not so easy, but I've found it for you!
According to this thread, the Rogue's answer, socket notification is also done with task signals, so I think that you should give a long vacation to WaitSelect(), check the signal number of the socket, create a mask with all signals you need, and give a chance to Wait()...

The other solution could be two tasks - one for socket, the other for GUI. But you'll have to make yourself a possibility to wake up the task waiting on socket somehow, at least to have the ability to close it, while the is no activity on socket.

But to be honest - I have NULL Reaction experience.

Good luck

[PiR]

Hi again.

I did downoad AmiTCP_SDK just to look at it.
Ok, there is no way to find this signal out of the socket.

According to this thread, what Karlos is saying is that Reaction does some stuff in input.device task, which may mean even not signalling your task. Check it with some gadgets that HAVE TO be propagated to your task, like CloseWindow.

If this is case, then I think you'll have to make your own additional signalling.

Good luck

[xeron]

Personally, I try to stay away from the WaitSelect() method. Instead I set up a socket event mask with SocketBaseTags, and use asynchrous non-blocking sockets. That way you can just use Wait( signal_mask | reaction_mask | whatever_mask ), and then see what needs attention.

[jahc]

How do you setup a socket event mask with SocketBaseTags() ? I'm reading the autodoc but I cant work it out.. sorry!

That sounds like a good way to do it though. Nice and simple to program.

Thanks everyone for your help so far..

[xeron]

e-mail me at "pete at petergordon dot org dot uk" and i'll knock up a simple example and email it in a reply. I can't help right now because I'm at work...

[jahc]

Thanks for your help by email xeron..

My program works well now on my comupter, BUT it wont run on my friends computer.. It looks like the signal isnt getting through somehow..

if( ( socksigbit = AllocSignal( -1 ) ) == - 1 )
{
   printf( "Unable to allocate a signal\n" );
   return FALSE;
}
socket_signal = 1 << socksigbit;

Should the above line be 1L instead of just 1? Does it make a difference?