V1

7 ms·

1.
Ekke, a new test runner for React-Native(godaddy.github.io)
5 points by V1 7y ago|0 comments
2.
by V1 12y ago
To bad that networks/proxies usually block websocket connections causing this solution to fail.
3.
by V1 12y ago
You could also just use Primus which exposes a Stream compatible wrapper by default for the client and server. https://github.com/primus/primus (Primus uses engine.io,sockjs,browserchannel,websockets internally so you&
4.
An attack on publisher freedom and the power abuse/misuse by npm Inc.(medium.com)
11 points by V1 13y ago|3 comments
5.
by V1 13y ago
Even Google is using it ;)
6.
by V1 13y ago
Thanks for you feedback, I did do some testing with multiple backends (4 different servers) but it didn't show any substantial changes. I'll see if I can do some in depth in a while.
7.
by V1 13y ago
I'll be more then happy to see if my configurations can be tweaked. And I was surprised as well, but it seems that it always boils down to the configuration files a small change can sometimes yield great results as seen with a specifying ci
8.
by V1 13y ago
It's not a `local` server. The proxy, websocket server and the benchmark utility are all on different servers.
9.
by V1 13y ago
The `http-server-close` option did not change anything. But by adding the ciphers it was able to squeeze out the same performance as Nginx. I'll update the tests accordingly. Thanks for the heads up!.
10.
by V1 13y ago
hipache is build on top of http-proxy. That's why I haven't included it in the tests. They have seem to have switched to a fork of http-proxy but there aren't big (if any) performance modifications as far as i've seen from the commits.
11.
by V1 13y ago
I'll re-run the test with the advised changes and see if the performance improves.
12.
by V1 13y ago
Because we people obviously don't have a datacenter in our own basement. And the common mistake people make when benchmarking is running the servers on their own machine and then use the same machine to benchmark the server it's running. Yo
13.
by V1 13y ago
Are you referring to the cipher verification? I used: openssl s_client -host localhost -port 8082 Which is a openssl command. These settings were used for testing SSL: https://github.com/observing/balancerbattle/blob/master/ngin...
14.
Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support(github.com)
81 points by V1 13y ago|38 comments
15.
Versions: The Node.js Content Delivery Network(blog.nodejitsu.com)
6 points by V1 14y ago|0 comments
16.
by V1 14y ago
Backed. Like everybody who touches JavaScript should do. Also. mmmm finally decent vim bindings for javascript? I do wonder how it will compare to Eclipse Orion's JavaScript content assist which is using Esprima as parser. http://contrapti
17.
by V1 15y ago
you can just as easily spawn multiple node.js servers and kill off the unresponsive one's
18.
by V1 15y ago
Great! Now everybody who wants to have information about Node.js has to scroll a shit load down and search for an oddly placed menubar on the right side.. Because who would expect a menubar with vital information such as docs above the fold
19.
by V1 15y ago
Socketpuppet #13242 reporting for duty sir. It's great preso btw, did it get recorded?
20.
by V1 15y ago
Hi, Could you describe was buggy about the demo? Did it load really slow or was it something else :)? I'm currently working really hard on the commercial version of Observer which will be much more speedy less hacked up. So any feedback is
21.
by V1 15y ago
Lazy load it. It's not the thing that users will be doing when they first load you page anyways.
22.
Hiding the web, one page at a time(github.com)
21 points by V1 15y ago|3 comments
23.
by V1 15y ago
Google Dart was designed to build large scale web applications, yet all their demos and example code only includes small applications. That still require quite a lot of code to build. I don't see any profit of building a application in dart
24.
by V1 15y ago
\o/
25.
by V1 15y ago
Thanks, glad you liked it! I managed to pull it off thanks to a lot of planning. Btw I won solo / overall (and also became first in utility) :)!
26.
by V1 15y ago
Hi, I am going to continue working on it, the service still needs a lot of polish and tests (didn't have time to write those yet). It's most likely going to be paid service based on the amount recorded sessions. Or I'm going for a amazon ba
27.
by V1 15y ago
It's probably because Chromium is shipping with a different WebSocket specification which isn't supported on some hosting providers yet.
28.
by V1 15y ago
Thanks, Glad you liked my entry. I personally think that Node's sweet spot is more real time than analytics. Analytics is just one of the things people want, in real time ;D
29.
by V1 15y ago
Yes I noticed that as well, but I found that the name observer really suited this service. But I'm still searching for alternate names to avoid potential confusion.
30.
by V1 15y ago
Yes I plan to continue development of this application after the competition, there are still some rough edges that needs to be fixed. So I see this a great working prototype to iterate on. I still have some amazing ideas planned :)

More ›