Skip to Content.
Sympa Menu

ndt-dev - [ndt-dev] Advice in resolving issue #102

Subject: NDT-DEV email list created

List archive

[ndt-dev] Advice in resolving issue #102


Chronological Thread 
  • From: Sebastian Malecki <>
  • To:
  • Subject: [ndt-dev] Advice in resolving issue #102
  • Date: Tue, 11 Feb 2014 10:25:57 -0500 (EST)

Hi.
I've just try to resolve problem from issue #102. The main problem isn't
difficult, but I'm not sure what to do with Jakub suggestion
(https://code.google.com/p/ndt/issues/detail?id=102#c1).

1.
Do we need "SRV_QUEUE_SERVER_BUSY_60s", which is only implemented in clients,
but it's never send by server. It's even not in documentation
(https://code.google.com/p/ndt/wiki/NDTProtocol#Queuing_clients).
Please let me know if I understand because "Server Busy: Please wait 60
seconds for previous test to finish" is not precise enough for me. Busy_60s
should be send if server drop the connection and client try connect faster
than 60s? Only after "9988" message or also after "9977"?

2.
And question about: SRV_QUEUE_SERVER_FAULT. In most places server send 9988
(SRV_QUEUE_SERVER_BUSY), but in my opinion it should be send only from:
https://code.google.com/p/ndt/source/browse/trunk/src/web100srv.c#2291, right?

In my opinion "9977" should be send from:
https://code.google.com/p/ndt/source/browse/trunk/src/web100srv.c#2030
https://code.google.com/p/ndt/source/browse/trunk/src/web100srv.c#2049 (as in
the command)
https://code.google.com/p/ndt/source/browse/trunk/src/web100srv.c#2083



Archive powered by MHonArc 2.6.16.

Top of Page