nimforum mirror - A doubt on Selectors

Arrrrrrrrr (orginal) [2015-07-30T21:59:31+02:00] view original

I programmed the above snippet to learn more about sockets and selectors in nim. In my example, server sleeps for 5 secs and then displays on the screen any message received. Client will send a message to the server via command arg (that is, i open a socket, send a message, and close it)

Now, if while the server is asleep i send 2 messages, next time the selector selects it will only display one, sleep for 5 secs, and display the other message.

I have tried to make the socket non-blocking and trying to read more than once using recvFrom, but it throws an expection. Give me a hand please.

gmfawcett (orginal) [2015-07-30T22:29:56+02:00] view original

Just curious: why is your server sleeping at all? That's not typical for a server, and could be contributing to the problems you're seeing.

Arrrrrrrrr (orginal) [2015-07-30T22:50:14+02:00] view original

It is not that strange in videogames.

dom96 (orginal) [2015-07-30T23:36:47+02:00] view original

Why are you using selectors and the net module? Just use asyncdispatch + asyncnet.

Arrrrrrrrr (orginal) [2015-07-30T23:45:01+02:00] view original

I dont have experience with the asyncnet module and im not sure if it will fit my needs. I will have a look at it, but before i'd like to know how to fix this problem.

Quikli (orginal) [2015-07-30T23:53:37+02:00] view original

The standard library calls the asyncdispatch and asyncnet libraries "largely experimental." Is this not the case anymore? I've wanted to use the asyncdispatch and asyncnet libraries in the past but was scared off by the "largely experimental" warning.

dom96 (orginal) [2015-07-31T00:36:26+02:00] view original

@Arrrrrrrrr just noticed that you're using UDP, asyncnet doesn't support that yet so fair enough. Things I see wrong with your code:

You're using sleep, that blocks your thread, you should instead set a timeout in select.

Your sockets are blocking

@Quikli Perhaps it is time to get rid of that warning. This forum uses asyncdispatch and asyncnet extensively and it's working fine. There are still some issues to do with try statements in async procs though. In general though, it's pretty solid.

Quikli (orginal) [2015-07-31T01:29:51+02:00] view original

@dom96 that's good to know. I'll give it a shot the next time I need something async. I tend to work with things that throw exceptions very rarely, so the outstanding issues are unlikely to impact me.

Arrrrrrrrr (orginal) [2015-07-31T11:44:33+02:00] view original

If this is to be trusted http://www-01.ibm.com/support/knowledgecenter/SSB23S_1.1.0.7/com.ibm.ztpf-ztpfdf.doc_put.07/gtpc1/block.html my error is just to be expected, so i included try-except to catch when there is nothing more to read and moved on. Thanks for your help.

Mirror of forum.nim-lang.org

1481 :: A doubt on Selectors