ay

86 ms·

571.
by ay 16y ago
For the most scenarios the maximum number of connections between the same client and server will be smaller, because an unbound client socket would reside in the ephemeral port range: http://en.wikipedia.org/wiki/Ephemeral_port
572.
by ay 16y ago
"Patterns and table.concat can get a lot done" - sure. but it is may feel somewhat backasswards :-) $ time lua -e 's="";for i=1,100000 do s=s.."-";end' real 0m1.292s user 0m1.029s sys 0m0.108s $ time lua -e 't={};for i=1,100000 do
573.
by ay 16y ago
Strings operations is a tricky part though. It's easy to slow the code down with "obvious" coding - which is a bad thing in a language. Some other operations like metatable lookup might not be always the fastest. But overall the convenience
574.
by ay 16y ago
I think those who find it a productive tool, just use it without waiting for the whole herd to head that direction - and since it's just a tool that provides a productivity edge - why advertise too much about it on blogs ;-) http://www.cis
575.
by ay 16y ago
In this case, you would be looking at PHP and Java, not node.js. Last time I checked node.js and libraries for it (about a couple of months ago), I could not run the library I wanted on the latest version of the node.js because the API has
576.
by ay 16y ago
The documentation that is there on the site is absolutely excellent - first there is a document that can get you a running server within a few minutes: http://mongrel2.org/wiki?name=GettingStarted Then there's a complete manual which take
577.
by ay 16y ago
In this case Zed made a design decision to have a common target format for the config (which I personally applaud). Doing what you propose would only bring extra clutter to those who do not have the social problem that you propose to solve
578.
by ay 16y ago
I tried on #3 the most inefficient algorithm I could come up with - blindly going through all possible combinations and checking if their biggest member is equal to the sum of the rest. Time of the execution: 0.6s I am not sure if this st
579.
by ay 16y ago
This relates back to the discussions on http://news.ycombinator.com/item?id=1742305 - where we did agree about business being the judge for "to 6 or not to 6". This case is an interesting example of that - though at this point it is still
580.
by ay 16y ago
You can remove the -00 and look through the history of the doc - it's now at a later revision.
581.
HSBC upgrading their infrastructure to IPv6(v3.co.uk)
1 points by ay 16y ago|1 comments
582.
by ay 16y ago
"This sentence is self evident, almost a tautology." - Ok, probably I misinterpreted your comment about the NATs being evil, apologies. "About the load balancer, wouldn't the problem be solved with SRV records?" - the SRVs would certainly h
583.
by ay 16y ago
I am not a sales guy. Surely you will he fine with NATs for some time. But this time is not infinite. And when it ends, you will be up for a harsh awakening. So, plan which of the scenarios is more appealing to you. If you plan a parachute
584.
by ay 16y ago
(a) - When she would have to choose whether to pay $10 or $30 per month for the facebook. (b) - Experience, when down the road a year or two from now it will mean some real eyeballs. If you do not care about serving to mobile users, no need
585.
by ay 16y ago
"They're void of content" - no, they are just a restatement that any technology is only as evil as its use. Think P2P. One can argue it is evil because its predominant use is to distribute pirated content. But it is not. Similarly, nukes we
586.
by ay 16y ago
The problem is not in the low-level applications - porting them is doable ( http://gsyc.escet.urjc.es/~eva/IPv6-web/ipv6.html ) The problem is in the library frameworks that do not give at all the means of making an IPv6 socket. Once that p
587.
by ay 16y ago
It depends on the economic (dis)incentives around such an action, and they will be the main determining factor, as opposed to technicalities. Whether it will be much easier with IPv6 than with IPv4 - the time will show. Much like with the a
588.
by ay 16y ago
For the "I'd bet that a small group of dedicated engineers could come up with an compatible extension to IPv4" I quote the [1]: "There is no such thing as an IP protocol with extended addressing that is on-the-wire compatible with IPv4." [1
589.
by ay 16y ago
http://www.out-law.com/page-11052 It is marginally more difficult than IP addresses. So, unless you are truly using a multiuser machine from which the users use the Internet, it's just a convenient feeling of security. Which in itself doe
590.
by ay 16y ago
Nice to see the specific data. Another data point: last year at FOSDEM we had more than just a couple of v6-connected hosts, here're some stats I kept for fun: http://stdio.be/onsite.fosdem.net/ Needless to say, noone ran after the confer
591.
by ay 16y ago
IPv6 on iPhone 4: http://www.fix6.net/archives/2010/06/22/ipv6-on-iphone/ For the learning: take a look at http://www.6deploy.eu/index.php?page=tutorials - they seem pretty nicely readable, maybe you can use those materials. Curious abo
592.
by ay 16y ago
I have reread my message above and do not see me stating the assertion you are arguing against. Mind to clarify your logic ?
593.
by ay 16y ago
Nice analysis. And locator-ID split idea in (3) is fun. However, (3) is tricky in itself - you still need the routing info to come from somewhere. And, would not matter too much whether it is IPv6 or another layer of IPv4 that are used as l
594.
by ay 16y ago
everyone is not going to keep the persistent block of addresses. everyone with an AS# and BGP might - same as now for IPv4. everyone who is single-homed to the same ISP - just might as well, since they will be using provider-assigned sp
595.
by ay 16y ago
However, depending on your business, you might want to be careful. At a minimum, clamp the MTU on the server to be less than 1500. There is still a fraction of clients that will be broken by this process. I run a small service which you can
596.
by ay 16y ago
"market based allocation" - this means further deaggregation of the existing prefixes. Which translates into eventual serious capital expenditures for the carriers to hold the large tables. Worldwide. In addition to the money required to pa
597.
by ay 16y ago
I am one of the authors of a draft that describes how to make the transition, at least for the "client" apps (like HTTP), more straightforward: http://tools.ietf.org/html/draft-wing-http-new-tech Also, for the rogue RAs, there is a soluti
598.
by ay 16y ago
Not sure if original link is direct to seating - but if it is, it does not render on my HTC desire with Android 2.2 and mobile safari. I use Raphael on one of my websites and have similar problem there.
599.
by ay 16y ago
Yes, I have just replied to the sister comment - I think this is precisely what makes the difference in perception.
600.
by ay 16y ago
I meant to compare the end result, not just the wording - apologies if I did not express it clearly. I think I found a way to put it differently: in one case it is the user that lets the company collect the data, in the other case it is the

More ›