i brought this up to start thinking about architecture... i think you have 3 basic ways to handle this:
1- the js just talks to an API which delegates what is allowed or not 2- each python class has a an internal dict/array/etc of the externally available functions that it allows access to. the js items are just subclasses. 3- a crazy thing that i sometimes to is more like a MmVC model ( i made that up just now! ). sometimes i push a bunch of 'controller' logic into the model, and then have the model access/manipulate the ORM/DB stuff. this way your app code never touches sqlalchemy or anythign else outside of the model class; and the controller manipulates the model stuff. i did that a lot more in perl than pylons, because I'd use multiple ORMs in a single project. under this approach, you could just subclass the models for use under js, and lockout/enable certain aspects --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
