>
> Realistically Django is probably the safer option if you are on the fence.
> It's more widely used and has more resources available.
Following your logic, they should migrate to PHP :) - it's more widely used
and has more resources available.
web2py works well out of the box and is used by a lot of people, is backward
compatible,
and his core functionality (dal, views, ) is very stable and there was many
cycles in bug fixing (almost every 1-2 weeks)
At this point, I think Web2py needs a champion to work out well.
I think you are really, really wrong, this is about to say about django, I
couldn't get started with it because there was not an expert around to help
me
Newbies can very quickly get started with web2py, and it is very
intuitively,
and you will hardly find a more friendly mailing list than that, Massimo
itself will help you if you have troubles
I will be happy to read their views, especially in management,
deployment and DAL / ORM
deployment: cgi, fcgi, wsgi, standalone (has his own webserver)
I use dal with rpc services(amf and xml) in a few Flex projects
'models/db.py'
db.define_table('t1', Field('f1))
'controllers/gateway.py'
def call():
return service()
@service.xmlrpc
@service.amfrpc('myservice'
def get_list():
return db(db.t1).select().as_list()
and you have both xmlrpc and amfrpc services,
I think this is even not documented (that you can use both at the same time)
and if there are errors in services , there are error tickets that helps me
to find and fix bugs
