@Mr2 不是二代一般不会这么有钱的，给别人做外包才有一定的闲钱...

@aerolqr 原来如此...

@ultragtx 原来如此，还以为从Air开始，太小白了...

@flypiggy 受教...

手机敲代码...狂拽酷炫吊炸天！

铃木俊隆《禅者的初心》
山下英子《断舍离》

@hustlzp 啊，不好意思，我回的是你的《黑客与画家》...我觉得新版的封面太丑了，完全和第一版的没法比...

@aku 看一眼就要吐了

angular.js
Android

@arbipher django的话应该很成熟了，github上搜一下。

Flask的话，Flask-Principal这个插件不错。

http://pythonhosted.org/Flask-Principal/

@wubo19842008 感谢分享，让我知道还有RBAC这个概念...

找到中意的工作
个人技能和个人项目要有大进展
找到真爱

@dawncold 是的，赞同你的看法。我目前的设计就是只存储文本。

@gfreezy
@alex321

目前是第一种情形，所以无需动用message queue。

后面要做“动态关注”的话，估计用户多了就得上消息队列。

@alex321 恩，我在这方面经验太少，得找他们请教下~

过段时间会把notification的实践经验分享出来

@alex321

系统中维护一个公用的消息任务队列？有消息产生就往队列里塞，队列的worker负责处理并分发到各user？是这个意思吗？

在stackoverflow上看到的一个回复：

http://stackoverflow.com/questions/1315991/design-pattern-notification-system

"Create a system queue, each message added to this queue has a list of "consumers" and the content. The main message pump processes each message and sends the message to all consumers.

Lets say 2 people befriend each other. You add a message to the main system queue that A is friends with B and consumers are both A and B. When your message "pump" (processor) sees this message it adds it to the queue of A and the queue of B. So now user A and user B have a new message that they are friends. In turn each user has a message processor, so when it sees a message called "I am friends with [someone]" it processes this as add a new entry to the "wall" visible to friends of A that "A is friends with B", etc.

This is overly simplistic but hopefully shows how message queues can be used for this (very similar system is used as the windows UI framework) so there is already an existing example and there are plenty of synchonized message queue patterns you can use."