hello friends, indeed, breaking each application in a collection of services doesn't allways seem the best way to go. it would at least involve another python process for every such process, and python is indeed a memory hungry engine, and that additional service would not necessarily be shared between different applications, which may frequently have different databases.
moreover, the authentication and authorization may frequently have additional relationship with the application (at the model level, at least), and thus be reasonable to be kept, if not otherwise defined, with the main model. thus i'd rather keep the current framework [optionally] functional at all levels: not only as an additional interface to an external service. hope that's not a too conservative way of thinking, alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
