piotrSikora

8 ms·

31.
by piotrSikora 15y ago
What's wrong with the first Google's response for "HTTP status codes" (i.e. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html )?
32.
by piotrSikora 15y ago
Who doesn't store files in "the cloud" nowadays? You could as well call this "Gmail for Hackers"... it would make as much sense as your "Dropbox" analogy. Why don't you call it by name (i.e. "hosted RubyGems server") instead of confusing pe
33.
by piotrSikora 15y ago
Sorry, but how is that "like Dropbox for Hackers"?
34.
by piotrSikora 15y ago
HTTP/1.1 doesn't mean WebSocket support (which nginx doesn't do right now).
35.
by piotrSikora 15y ago
Head's up, I've started working on both: - PUSH/PULL + PUB/SUB support for ngx_zeromq (transport module), - ngx_mongrel2 (upstream module). Should be ready sometime next week.
36.
by piotrSikora 15y ago
> if the restrictions that this new module places on it (namely, exclusively REQ/REP pairs) make that not apply. ZeroMQ I/O threads are still being used with REQ/REP, so this doesn't change anything in that matter. Also, exclusive use o
37.
by piotrSikora 15y ago
> Also, the fact that ZMQ is message, not stream, oriented makes it non-ideal here. You get the whole response in one big chunk. Across an internal network, this may not be a huge deal, but it's not a desirable property. ZMQ and ngx_zer
38.
by piotrSikora 15y ago
Proof-of-concept, nothing else at this point.
39.
by piotrSikora 15y ago
> it's very feature poor as compared to Mongrel2. One could not simply swap in nginx with this module for an existing Mongrel2 installation. That's because this is _transport_module_ and what Zed did with Mongrel2 is build a level 7 pro
40.
by piotrSikora 15y ago
> How is this different than Mongrel2? It has nothing in common with Mongrel2 other than the fact that both use ZeroMQ transport instead of TCP.
41.
by piotrSikora 15y ago
> Cool stuff, but I'm wondering why they went with REP/REQ instead of ROUTER/DEALER. Because this is just proof-of-concept hacked over 2 days (+ README file). It probably wouldn't be even released at this point, if I didn't promise it t
42.
by piotrSikora 15y ago
Theo Schlossnagle's "Career Development" (Velocity 2011 Keynote): http://www.youtube.com/watch?v=y0mHo7SMCQk
43.
by piotrSikora 15y ago
It also misses NSElite (later Teamware), which, in Larry McVoy's words, was BitKeeper's grandparent.
44.
by piotrSikora 15y ago
You guys should really look into http://betterthangrep.com/ :)
45.
by piotrSikora 15y ago
So you're saying that unencrypted DNS traffic is more secure than DNS traffic encrypted using questionable algorithms?
46.
by piotrSikora 15y ago
Why do people keep linking to GitHub repos instead of official websites? http://amon.cx/
47.
by piotrSikora 15y ago
...and why exactly does it depend on bash instead of sh?
48.
by piotrSikora 15y ago
You seem to miss the difference between "developer testing his/her app" and "everyone testing every app". To the point, I'm using "/etc/malloc.conf -> AFGJPRX" on most of my systems, which means that virtually everything that runs there
49.
by piotrSikora 15y ago
There is huge gap between "enough demand for a service" (few thousands) and "majority of China" (half a billion).
50.
by piotrSikora 15y ago
> my understanding of what a majority of the people inside China actually want. Do you really think that the majority of Chinese citizens use VPNs to bypass the firewall?
51.
by piotrSikora 15y ago
It's not? How about: * passwords required to connect to the IRC server, * passwords required to use given nickname (enforced via NickServ), * SSL.
52.
by piotrSikora 15y ago
Solaris is written in C. Same is true for all BSDs, PostgreSQL, nginx and a lot of other high-quality software.
53.
by piotrSikora 15y ago
"Business as usual."
54.
by piotrSikora 15y ago
OP didn't mean GitHub changes, but "beautiful" commit ids (0001..., 0002..., 0003..., etc).
55.
by piotrSikora 15y ago
But if it would be extremely easy to port kernel-level features from one BSD to another, then it would mean that their code doesn't differ too much and there would be no point in having multiple BSDs in the first place...
56.
by piotrSikora 15y ago
Yeah, I like it that way as well. Sadly, this means that you'll always miss some killer features that are available in other BSDs (FreeBSD's jails, NetBSD's puffs, DragonFly's HAMMERFS).
57.
by piotrSikora 15y ago
...or Drizzle.
58.
by piotrSikora 15y ago
Is it only me or the latest iteration of "Platform-as-a-Service" offerings doesn't differ at all from shared hosting?
59.
by piotrSikora 15y ago
Blame your distribution for that, not C... On OpenBSD "it just works (tm)": $ ulimit -c unlimited
60.
by piotrSikora 15y ago
SmartMachines == OpenSolaris / SmartOS (their IllumuOS-based distribution). Also, they are actively developing and co-sponsoring IllumOS (and are IMHO the only reason why it didn't die yet), so next time do some research before bashing on a

More ›