> So I guess I'm just curious to hear how other members of the > community have solved this. Are people slipping business logic into > the model classes for the most part?
If what I need to write doesn't really fit in any of the common "places" (models, managers, views, middleware etc.), then I would say you are free to put it wherever you want to. I don't think there would be anything wrong with using, say, ./project/app/services/facebook.py. Or just ./project/services/facebook.py if it's not specific to an application. I know some people are creating separate apps (within their project) for that sort of thing. I guess that makes most sense if you can map sub-parts of what you implement to Django pieces. Say your Facebook functionality wants provide it's own set of template tags. Or a callback view for the API. Or if there is a chance it *might* need it's own model at some point. For a Facebook client that possibly doesn't even depend on your project, you might even want to consider a separate reusable package. Michael --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
