Good day. I'm new here, as well as a new (all of two months of
experience) Python web app developer.
I'm interested in porting a Google App Engine
"google.appengine.ext.webapp"-based app to a standalone Django app on
another platform. I've ported my data models from GAE to Django, as
well as my data access objects. And I can see from here what I would
need to do to port my url routes currently expressed through
application = webapp.WSGIApplication([('/admin/account/register',
admincontroller.AdminRegisterController),], debug=True)
to a set of routes in the Django urls.py file. (Aside: could I
actually keep the WSGIApplication router, too?! If yes, how?)
What I am interested in now is preserving as much line by line code in
my various controllers (e.g.,
admincontroller.AdminRegisterController). I'm less concerned about
building http response objects by hand in Django as I am about the
function vs. class routing disparity between Django and GAE webapp-
based routing. As I read the Django book by Holovaty, et al., the
urls.py routes take a regex url path and maps it to a function.
Whereas the the GAE routing maps a regex url path to a class that
implements handlers for GET, POST, etc.
Since I'm new at all this, I did not have the foresight to build in
any abstraction as a hedge against a future port. The app isn't that
large, though, so porting it brute force to use functions instead of
classes in the routing table is not that big a deal.
Can anyone talk about how I get there from here re the routing
semantic disparity?
Thank you.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
