Lexin Gong gonglexin

Routes

小心地使用 Match（Rails 3 已实现）

Rails 3 提供了 match 方法供我们自定义 routes，然而我们要小心使用它以避免“跨站脚本攻击”（XSS Attack）。比如像这样的 routes：

注：（r3 代表 Rails 3，r4 代表 Rails 4）

# routes.rb

Rails 4 - Active Record Associations

has_one

一对一关系：有 A 和 B，A 拥有且仅拥有一个 B

belongs_to

Models, Roles, Decorators, and Interactions

A modest alternative to DCI that might be worth further thought

One of the problems with advancing the discussion on DCI is that we lack a comparable alternative pattern that has the same goals, but favors a low ceremony approach. The closest thing we have to that is Rails concerns, but they are more like distant relatives of the DCI concepts rather than first cousins, and that makes comparisions between the two approaches not especially fruitful.

I am considering the idea of experimenting with my own paradigm that captures the intent and purity of DCI, but with the convenience of concerns. Please note that this is just the starting point of a conversation, it is NOT a promise of comercially available cold fusion or a cure for cancer. It's just a gist with an idea on it I'd like to hear your thoughts on.

What if we had a top-level topology that was split into Models, **Rol

下面是陈首席陈临怀发表在微博上的 [NetScreen的往事]，我在看的过程中将其拷贝出来，整理成文，方便想看的人一口气看完。微博见：http://weibo.com/huailinchen

［NetScreen的往事］下午要在厦门见邓锋。突然又想起了许多NetScreen的往事。我是一个能写代码的文艺青年。决定在weibo上，来写写过去，算作为逐渐老去的我们的一点纪念。。。

［NetScreen的往事（1）］2001年的9月11日的早晨。我大概7点左右被人叫醒。纽约遭遇攻击！“。在电视上我看着第2架飞机冲入Tower Building，恍惚做梦一般。。。上午去公司。。。大家都很担心。知道NetScreen的创办人Feng和Yan也在纽约，处理公司上市的事情。大家都很担心他们。我们是兄弟。

［NetScreen的往事（2）］应该是中午的时候传来消息。他们已经跑到亚特兰大去了。在等待转机。。。大家都在等着他们的回来。记得是晚上7点左右，夏天的加州，依然天很亮。我和Shalang（现Juniper Beijing Director）在楼下抽烟。看见Feng和Yan下车了。。。我是个很感情化的人，冲上去拥抱了Feng。

［NetScreen的往事（3）］Yan是个比较严肃的人，而我的工作基本上是他和Yuming［Palo Alto创办人，今年上市，发大了］直接领导。他经常修理我。有点怕他。不敢和他拥抱。Feng很随和，喜欢开玩笑［含黄色段子］。大家都喜欢他。。。

Changes:

this version includes backport of Greg Price's patch for speedup startup http://bugs.ruby-lang.org/issues/7158 .

ruby-core prefers his way to do thing, so that I abandon cached-lp and sorted-lf patches of mine.
this version integrates 'array as queue' patch, which improves performance when push/shift pattern is heavily used on Array.

This patch is accepted into trunk for Ruby 2.0 and last possible bug is found by Yui Naruse. It is used in production* for a couple of months without issues even with this bug.

Sinatra like routes in Rails controllers

A proof of concept of having Sinatra like routes inside your controllers.

How to use

Since the router is gone, feel free to remove config/routes.rb. Then add the file below to lib/action_controller/inline_routes.rb inside your app.

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

	require 'date'

	author = "Saito"
	email = "[email protected]"
	date = Date.new(2012, 7, 30)

	s = %w{
	. . . . . . .
	. . o o o . .
	. o . . . . .

	I'd like some clarification about Ruby 2.0:

	* Is it intended to be a development release?
	* If it is not a development release, why are experimental features included?
	* Whether or not it is a development release, what process will be used to remove
	features after release? (For example, we still have $' and friends years after
	Matz has repeatedly said he wouldn't add them in retrospect.)
	* Why are APIs like IO.readlines not being fixed to use keyword arguments?
	* Why are API changes not being added to RubySpec?
	* Is Ruby 2.0 expected to pass RubySpec before release? (This does not allow for