Socket.IO[2] is more like SignalR compare to http-kit.
[1] jquery.signalR-1.0.1.min.js [2] http://socket.io/
Great work! I know it's quite complicated, but how are the plans for https support coming along?
Kudos to you and Peter on a great library!
For the server, https is not planed, since It's better be done by Nginx or something alike [1].
For the client, https is planed. We have use case for it, too. Some time is needed to work on it. It will come out in one or two month, I guess.
To tell the truth, I, Peter[1], and a few others take more than a month to think and discuss the API, even though there are just few functions to export. We try our best to make it better. In the end, I think, We are quite happy with what we get now: the unified API.
If a very good idea found to do the API, but the API would break, then it's version 3. But version 2 will still be maintained, and any bugs will get fixed. That's the promise.
Is this address your concern?
http-kit is a very small and focused library, It just do one thing: talk in HTTP. http-kit need to work together with other libraries like Ring[1] and Compojure[2] to do the server side.
Few good things about http-kit: 1. Very fast and scalable, almost as fast as what you can get from the hardware. 2. Focus, do one thing and do it well, thing about Linux/Unix's philosophy. Personally, I prefer this way of doing software.
[1] https://github.com/ring-clojure/ring [2] https://github.com/weavejester/compojure
