Thanks for the thoughts Preston!
> I think a base class with subclasses is the best approach. > > Define as much common behavior as possible, set up defaults for those > fields needed by your outbound API Indeed, thanks for the confirmation. I think it's time for experimentation! > How are you handling the branching lookup of what subclass to use? > You might name the subclasses in some way that they can be derived > from the partner URL - or some other way that intelligently selects > the subclass for you Incoming requests for processing would have associations with specific backend partners defined in the database and processed as part of the request, so the branching will be tied into this. > I assume you've looked at django-piston I had not seen it, so thank you for pointing me in this direction! ~Jason --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
