Comments for 赖洪礼的 blog

Comment on Rails 2.0, cookie session store and security by 基于CookieStore的session存储机制的安全话题 - IceskYsl@1sters!

基于CookieStore的session存储机制的安全话题 - IceskYsl@1sters! — Tue, 03 Jan 2012 16:14:50 +0000

[...] 最近在看一本《The Rails way》的书，其中关于session存贮机制一章中，对基于CookieStore的session存储机制持否定态度，认为其存在被破解和Replay attack的可能。就我了解的信息来看，这个观点是不妥的。最详细的一篇文章是写的laigongli写的这篇“Rails 2.0, cookie session store and security”，文章比较长，说的很详细，感兴趣的可以过去看看。其中主要观点为： [...]

Comment on Ruby vs PHP performance by watch nfl games live

watch nfl games live — Sat, 01 Oct 2011 21:47:03 +0000

Thanks a lot for providing individuals with an exceptionally breathtaking chance to read from this blog. It is always very amazing plus full of a great time for me and my office acquaintances to search your site more than thrice per week to learn the newest items you have. And lastly, we’re actually impressed considering the breathtaking tips and hints you give. Selected 3 ideas in this post are rather the most suitable we have had.

Comment on Saving memory in Ruby on Rails with fork() and copy-on-write by Why Ruby 1.8.7 isn’t memory efficient? « Computellect

Why Ruby 1.8.7 isn’t memory efficient? « Computellect — Sun, 11 Sep 2011 16:09:25 +0000

[...] outside the object. For more information checkout this. For a longer and better explanation, go here. Share this:TwitterFacebookLike this:LikeBe the first to like this post. Tags copy-on-write, [...]

Comment on Ruby vs PHP performance by PHP开发工具大全（经典呀！不看后悔呀！） - WEB开发笔记

PHP开发工具大全（经典呀！不看后悔呀！） - WEB开发笔记 — Tue, 30 Aug 2011 14:30:21 +0000

[...] PHP是使用最为广泛的开源服务器端脚本语言之一，当然PHP并不是速度最快的，但它却是最常用的脚本语言。这里有50个有益的PHP工具，可以大大提高你的编程工作： [...]

Comment on Benchmark: Passenger (mod_rails) vs Mongrel vs Thin by Tyler

Tyler — Sat, 27 Aug 2011 05:25:45 +0000

This isn’t an apples-to-apples comparison.

These results reflect, to a large degree, the level of concurrency employed. With only 10 pools in the mongrel cluster, you can serve at most 10 concurrent requests. But you’re sending 100 concurrent requests! Apache, on the other hand, is by default configured to handle 150 concurrent requests. So it’s no surprise that the mechanism that uses Apache’s process space is faster.

If, on the other hand, you either increased the mongrel pool size to 100 or tested with only 10 concurrent requests, you would see just how well it ACTUALLY compares to passenger/mod_ruby.

Comment on Ruby vs PHP performance by PHP开发工具。 | suliuer

PHP开发工具。 | suliuer — Mon, 08 Aug 2011 18:28:20 +0000

Comment on Ruby vs PHP performance by dean

dean — Thu, 14 Jul 2011 16:20:07 +0000

Ruby is marginally faster than PHP until you do anything with the database. If you’re using Rails forget about performance.

Of course I’ve seen many, many other benchmarks of Ruby 1.9 and 1.91 that show it as significantly slower than 1.8.6 too, so I’m not sure if this is even legit or not.

Comment on Potential problems with preforking Ruby on Rails by James Pharaoh

James Pharaoh — Tue, 12 Jul 2011 07:16:57 +0000

Leaking IO handles is a problem I’ve had, and generally it’s only a problem when the child process is a daemon. For example, I start a background process from a web server, then the web server ends. The child process inherited the open server socket from the web server and still has it open. The web server can now not start again because the socket can’t be reopened on the same port. There are many simiilar situation which can arise from the same.

This isn’t really a ruby thing but a general unix processes thing. Basically you need to close any open IO handles after forking before executing a new process.

Comment on 3 Node.js gotchas that I’ve found in the past 3 days by 3D Drawing Pad

3D Drawing Pad — Wed, 18 May 2011 01:16:53 +0000

Hello Hongli Lai, i was wondering if you knew how to program web apps? Please contact me so we can talk
thanks

Comment on validates_uniqueness_of does not guarantee uniqueness by Hongli

Hongli — Fri, 08 Apr 2011 08:34:54 +0000

I see it as a limitation in SQL. It has no explicit support for “upsert” commands (a name for the concept “update or insert if not exist”, which is what this use case is all about). When those two SELECTs in the above example are being executed, it is impossible to know beforehand whether they are regular SELECTs or whether they’re part of an upsert command. Databases try to optimize for the highest concurrency, therefore they treat them like regular SELECTs and don’t isolate.

Running SELECT … FOR UPDATE on the other hand does work, and it signals the database that an upsert is imminent. However this is a non-standard MySQL extension.