> Of course I will continue using web2py, but will be great if I could use > it without problems when my applications demands more exigent use cases. Of > course, the most of the people do not think like me and begin to use > another framework that works either with small and complicated > applications, thats why they don't like and don't use web2py, not because > they are "purists". >
I'm not sure it's entirely an issue of small vs. complicated. Rather, I would say web2py is more focused on the development of new applications rather than taking over legacy systems. So, web2py has very simple default routing along with an easy to use parameter-based router to handle most common use cases, but if you need to replicate a wildly different URL structure from a legacy application that is being replaced, that may be more complicated in web2py (though in this case, I still think possible). Similarly, the DAL works best with database tables that have a single primary key field with auto-generated values, and so may have some limitations when working with legacy database systems that lack that structure. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
