mirror of https://framagit.org/bortzmeyer/echoping
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
56 lines
1.5 KiB
Plaintext
56 lines
1.5 KiB
Plaintext
Actual bugs are registered at SourceForge:
|
|
|
|
http://sourceforge.net/bugs/?group_id=4581
|
|
|
|
To see a given bug (say #132001):
|
|
|
|
http://sourceforge.net/bugs/?group_id=4581&func=detailbug&bug_id=132001
|
|
|
|
-------------------------------------
|
|
|
|
grep -i TODO *.{c,h}
|
|
|
|
is interesting, too.
|
|
|
|
------------------------------------
|
|
|
|
Wishes:
|
|
|
|
Display other calculations such as kurtosis.
|
|
|
|
Check the TCP timeout with T/TCP. Difficult to test, few T/TCP
|
|
machines exist. Timeouts on T/TCP connections are a bit experimental.
|
|
|
|
TCP timeout with long packets seem to confuse Cisco routers. Does
|
|
someone can reproduce it and perform tests? It seems to work now.
|
|
|
|
Do not display the end-of-line after the HTTP reply, for instance when
|
|
a page is moved.
|
|
|
|
UDP isn't really useable with large packets because of sockets
|
|
limitations and the lack of workaround code.
|
|
|
|
If a Web page is empty, echoping will display meaningless messages.
|
|
|
|
Since echoping writes everything to the server, then begins to read
|
|
the reply, some echo servers will timeout if you send very long
|
|
messages, because they expect you to start to read right now.
|
|
|
|
Make FLUSH a configure-able option.
|
|
|
|
Compiler's warnings:
|
|
|
|
1) Tru64's cc:
|
|
cc -DHAVE_CONFIG_H -I. -I. -I. -D_POSIX_PII_SOCKET -g -c icp.c
|
|
cc: Warning: icp.c, line 92: In this statement, the referenced type of the pointer value "(int ...)0" is "int", which is not compatible with "unsigned long". (ptrmismatch)
|
|
nr = recvfrom (sockfd, buf, DEFLINE, 0, (struct sockaddr *) 0, (int *) 0);
|
|
-----------------------------------------------------------------^
|
|
|
|
|
|
$Id$
|
|
|
|
|
|
|
|
|
|
|