gwl:start-gwl does not detect in-use port, crashes if one is already running
Created by: genworks
If a GDL is running with GWL webserver on e.g. port 9000 already, then a new one will crash when it tries to call gwl:start-gwl. This should detect the running server and roll to the next port (e.g. 9001).
By genworks on 2011-11-18 23:24:04 UTC
This seems to occur only on Linux and Mac, not on Windows.
By genworks on 2012-02-11 21:18:04 UTC
Removed :timeout argument to net.aserve.client:do-http-request in gwl:start-gwl. Apparently this argument is not supported in portableaserve. Still seems to be supported in native aserve, so not sure why start-gwl wasn't working in Allegro, but looks like it is now (as well as in LispWorks and SBCL).