Temporarily suspending feedlr for an overhaul
As some of you may have noticed, feedlr has the problem of sporadically repeating posts and it’s been happening more often recently. This bug is due to some mysterious errors that somehow skip my try/catch blocks and throw tons of stacktraces in the logs. Also due to the problem of there being too much noise in the logs from Grails and the lack of spare time I have lately, it’s been quite a pain for me to track down and eradicate this problem. And I feel very sorry for the users who have suffered from repeated posts.
The current implementation of feedlr is a result of the resource limitations of the server where it’s hosted, which is an everlasting problem for the Grails service. So I’ve always wanted to thoroughly refactor the code and find a better hosting service. With the problem of repeated posts aggravating, I’ve decided to temporarily suspend the current feedlr service while I migrate the whole site to Google App Engine, which means a rewrite of the existing code in Python.
This complete refactory (or rather, rewrite) won’t be completed very soon but I’ll make it happen as soon as I can. Meanwhile, I’ll keep this blog updated. Thank you very much for using feedlr and let’s meet again later on Google App Engine!
由于近期feedlr重复播发消息的问题变得严重，彻底重构feedlr的需求变得越来越紧迫。feedlr的实现是对于目前使用的服务器上有限资源的妥协的结果，随着feedlr支持的feed数量越来越多，服务器性能显得越来越突出。而由于近来我的时间非常有限，还有Grails在日志方面的过多噪音，我很难马上彻底解决重复播发消息的问题。对重复播发给大家造成的麻烦我深表歉意！
于是我现在决定暂时停止目前版本的feedlr服务，花一些时间把feedlr移植到Google App Engine上，彻底解决可扩展性的问题。由于需要用Python重写整个服务，需要花一定的时间。具体需要多久我也说不准，只能利用有限的时间尽快完成，请各位关注本blog，有更新会在这里发布的。在此对所有feedlr用户表示诚心的感谢，让我们在Google App Engine上再见！