koen

3 ms·

1. 1.▲
   by koen 15y ago

   I'm not to happy with this change though. At least with hixie-76, connections would fail to connect if the intermediate proxies are not understanding WebSockets. Now, your connection will succeed, both client and server will believe they ca
2. 2.▲
   by koen 15y ago

   WebSockets probably. None of the traditional server-side web frameworks (Ruby on Rails, Django, Java Servlets, ...) can deal with them because you need to maintain open connections with each client. That also makes asynchronous I/O importan
3. 3.▲
   by koen 15y ago

   > A big part of what empowers node to make these kinds of interfaces possible is its asynchronous nature. No longer do you have statelessness imposed from on high by the likes of apache or rails. You can keep intermediate state around i
4. 4.▲
   by koen 15y ago

   But bcrypt is just a few files of portable C (the .S is optional) with no dependencies whatsoever ?
5. 5.▲
   by koen 16y ago

   An author here. What drop-downs are you referring to? We are a server-side framework (GWT = client-side). That means there is no need to implement a client-server protocol to access server-side resources, which, as application complexity in
6. 6.▲
   by koen 16y ago

   I agree, the reverse proxies are becoming a bottle neck. Perhaps we need to team up and contribute it to nginx? It shouldn't be very hard unless their architecture really does not do persistent connections at all (they currently use HTTP 1.