Elver Loho wrote:
> In CherryPy, every "directory" of the website is mapped to a class
> with its exposed methods being the "files" in that directory. It's a
> godsend as you can write any kind of functionality (shopping cart,
> blog, whatnot) into a class or two and plop it anywhere else. Very
> portable and versatile.
>
> Django is somewhat more flexible (as you can map any function to any
> path), but CherryPy's class/method way of mapping things suits me
> better. It just seems more logical. Whereas Django allows you to
> redefine logic if needed :P
I think this is a drawback for CP. While "cool!" from the programming
side, you basically end up having your app structure become a public
API, right? So if you ever shuffle your app's structure you break
anything that was previously using or expecting anything from it. Or
you end up mod-rewriting, which is generally what the various
dispatchers do in the first place.
As you say, it's [a case of making users deal with] the programmer's
("more logical") view of the application, a sin covered better by
others elsewhere... clearly not world-ending, but more brittle over
time IMO. I do think I heard once upon a time that newer versions of CP
would be Route-able one way or another though... okay sorry all for the
tangent.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
