I want to try out Django for a small project, hoping to discover that it will be the web framework of my dreams, but I need some advice.
My project group has written an xml-rpc API in front of our database and password stores. This means that when we want to, say, create a campus guest account, we call xml-rpc functions like create_guest(), set_guest_info(), and set_account_password(), and those functions do all of the database operations (and sometimes operations on other systems) needed to perform each operation consistently (creating a guest requires at least six tables to be updated, for example). This is great in two ways. First, our business logic is all in one place, where complex operations get written once, correctly. Second, we wrote it in simple, plain Python that we could all agree upon, so that now each front-end and client can be written in the favorite language and framework of the group deploying it (so long as it talks xml-rpc), avoiding the need for a religious war and everyone being forced to use One True Platform. The problem is that Django seems to really, really want to talk to the database by itself. :-) At what level, then, would I subvert Django if, say, a Guest were not a row in a database table, but an entity that I get information about from an xml-rpc call, and for which some other xml-rpc calls let me set information? Thanks for any guidance! I'll be happy to write up my solution for the Django documentation page, which already discusses connecting to a legacy database - but not a ... what would one call it? A "legacy non-database." -- Brandon Craig Rhodes http://www.rhodesmill.org/brandon Georgia Tech [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
