--- old+++ new@@ -1,4 +1,3 @@-
Ocassionaly gnatsperl can hang if an expected response
code is not found, most of these were fixed in version
0.05 but some still remain.
status: open --> wont-fix
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Several code checks were fixed, and now the socket reader reads all output and then parses instead of trying to determine what's happening on the fly.
When working with gnatsweb, calls will be done asynchronously and timeouts/graceful failure will be worked from the frontend.
Afaik timeouts should be set on the socket connection itself. But I don't have any indication that it is an issue?
Closing.
Diff: