不要忘記 2
A case for breaking the web server ownership guidelines
I have to admit that there actually is a reason to break the goodpractice for webserver file ownership :the 404 handler trick for lightweight caching of semi-dynamic websites.
The 404 handler trick comes from three observations:
- most dynamic websites are in practice not very dynamic; the actualpages served change rarely.
- Apache (and other web servers) are many times faster at servingstatic content than dynamic content.
- Apache (and etc) can let you take arbitrary actions on 'page missing'errors.
很遠
和W孖公仔般clubbing快可慶祝周年紀念了,她看著我的「成長」。
不,不是這樣的。
那些男人的世界我全然不懂,我沒有相近的背景同樣的交際網。
我不是開玩笑,是真的
歌
這幾天,大家都覺得香港好像瘋了一樣。「住不得了」的聲音起此彼落。朗天便道,行開下囉
我沒有拍照。
Linux is a Unix
There used to be a meme going around to the effect that Linux isn't Unixand you shouldn't call it one (I say 'used to be' because I haven't seenit recently). This has always irritated me; not particularly because I'ma Linux partisan, but because it's such a small minded claim for Unixpeople to make.
When you ask people to support this, they generally point at tworeasons: Linux is not entitled to use the Unix trademark,
Properties relevant to finding what class supplies a method
For my own future reference if nothing else, here's someproperties relevant to finding what superclass supplies a method :
On super() objects, we have:
__self__ | the object you are calling super() about,ie the second argument. |
__self_class__ | the actual class of said object; equivalentto .__self__.__class__ but more convenient. |
__this_class__ | the class that super() was invoked for |