Tornado 2.1 released

#1

Post by dtwwtd » Thu, Sep 22, 2011, 6:19 AM UTC

Re: Tornado 2.1 released

#2

Post by rjd » Thu, Sep 22, 2011, 7:08 AM UTC

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

Re: Tornado 2.1 released

#3

Post by willvarfar » Thu, Sep 22, 2011, 7:35 AM UTC

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

I'm a convert from Twisted.

It is simple enough, the code is clear and small enough to dive into if you have any problems, and it works just great.

Re: Tornado 2.1 released

#4

Post by peterbe » Thu, Sep 22, 2011, 8:31 AM UTC

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

When speed isn't important and you know you want to use a SQL database; then use Django. For everything else, use Tornado. :)

Re: Tornado 2.1 released

#5

Post by JayInt » Thu, Sep 22, 2011, 8:54 AM UTC

peterbe wrote: post #4

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

When speed isn't important and you know you want to use a SQL database; then use Django. For everything else, use Tornado. :)

when he says Django he really means Flask :-p

Re: Tornado 2.1 released

#6

Post by halojones » Thu, Sep 22, 2011, 9:15 AM UTC

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

Easy to get started, easy to deploy, pythonic/magic-free code, responsive maintainer.

Re: Tornado 2.1 released

#7

Post by dirtyaura » Thu, Sep 22, 2011, 9:23 AM UTC

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

I've used both Django and Tornado and I vastly prefer Tornado.

Some personal experiences: With Django, I specifically don't like ORM and it's template language. Also, I thought the admin interface would reduce the need to write input UIs, but at the end of the day, it's not that suitable for end-user when you have several end-user roles with different access right patterns.

If you (read: I) are going to replace Django's template language and leave out ORM and admin interface out of Django, Django doesn't really shine anymore and simpler frameworks like Tornado provide cleaner base for your development.

Re: Tornado 2.1 released

#8

Post by zeemonkee » Thu, Sep 22, 2011, 9:50 AM UTC

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

I've noticed that Tornado comes with its own MySQL wrapper, however I'm concerned it might have blocking issues.

Does anyone have experience with using this ?

Also, what do people use for form validation with Tornado ?

Re: Tornado 2.1 released

#9

Post by oxfordus » Thu, Sep 22, 2011, 9:59 AM UTC

Coming from php(mvc background), the only thing i don't like about tornado is that basically you have a Class per request, currently i'm in a process to refactor this so that:

www.site.com/controller/action/params/?vars -> would route to ->

class controller(requestHandler):

    def get_action(self, *params, **vars):
        #do something
        self.write(response)
    def  post_action2(self, *params, **vars):
        #.... and so on ....

Re: Tornado 2.1 released

#10

Post by ergo14 » Thu, Sep 22, 2011, 10:19 AM UTC

dirtyaura wrote: post #7

rjd wrote: post #2

90% made up my mind to use Tornado for several upcoming projects, would love to hear some comments (good or bad) from anyone thats used it or using it.

I've used both Django and Tornado and I vastly prefer Tornado. Some personal experiences: With Django, I specifically don't like ORM and it's template language. Also, I thought the admin interface would reduce the need to write input UIs, but at the end of the day, it's not that suitable for end-user when you have several end-user roles with different access right patterns. If you (read: I) are going to replace Djang…

Hm, you could take a look at pyramid, if you dont like djangos orm or tempalting it might just be right for you.