#8 Consecutive TFTP GET's lead to timeouts

[gui]

Hello,

I have noticed that consecutive TFTP GET's to the same server from the same client lead to timeout. It seems the server does not response to the last TFTP GET request.

After enabling debugging, i see following message in the log:
'Hey, I am already working for you. Be patient'

After some more investigation, it found out that the problem lies in the usage of EventListener. After sending the last TFTP packet for a TFTP GET request, the server starts executing the event listeners. Meanwhile, the client sees that the TFTP finsihes and send the next GET request. But since the server is still handling the event listener for the previous get, it throws the message above.

It seems this behaviour only happens after a GET. Sending multiple PUT's (with event listener) is not a problem. But a soon as a GET is sent, the next operation (either GET or PUT) will fail. It's easy to reproduce by creating an event listener that sleeps for a while.

Note that this behaviour even occurs sometimes without using an event listener. Especially on Linux, these errors occur more often.

TFTP : v0.8