releaseAcceptSocket() doesn't cut availability of the server about swifter HOT 8 CLOSED

I've just tested it using demo iOS app and works fine for me. Anyway, could you please paste the code you use for testing ?

from swifter.

Sorry for the late answer; I can reproduce the mentioned behavior with the following sample code:
I figured out, that the server doesn't shut down only if there was a request before the server.stop() method is called. If you just start it and wait until stop() is called without performing a request, the server will behave as expected; the request will be refused.

Run the following twice, once just wait until the sleep(5) is over and then try to request the server, and once fire a request within the time of the sleep(5) (like http://localhost:9080) and try the same after stop() was called. The latter will answer twice (or more, it just seems to not release the socket).

import Foundation
var error: NSError?
let server = demoServer(NSBundle.mainBundle().resourcePath)

if !server.start(listenPort: 9080, error: &error) {
        println("Server start error: \(error)")
} else {
        println("Server started; try a connection now")
        sleep(5)

        println("main thread is awake again")
        server.stop()

        println("stopped server; try to connect")
        while ( true ) { };
}

from swifter.

ok. Thanks. I can reproduce it.

from swifter.

The problem is a while loop happening in case of "keep-alive" session.

from swifter.

I see. What do you think of a force-kill-switch like server.sleep(forceShutdown: Bool)?

from swifter.

I would like to extend server::stop() by closing all sockets.

from swifter.

This solves the problem:

b37392b

from swifter.

Great work! Thank you! :)

from swifter.