Hi, I have an annoying problem I've inherited that I'm trying to clean up. I'm looking for advice on the best way to clean it up.
We have a Django web app. It is essentially a view in a running log (call it *reader*) from a database. The db log is populated by an event queue (call it *writer*) on a different machine. All of the code involved is Python. *Writer* also processes other queue items that don't involve *reader * and it processing enough event items that indirecting through a service is probably not a good idea. *Reader* defines all of the tables using Django models. *Writer* includes all of the code from *reader* in order to access those model classes to insert items into the database. The problem is that the dependencies between *reader* and *writer* are somewhat opaque, and it gets even worse because there are clients of *writer * as well. This is of particular concern as we try to minimize what gets installed on *writer*. For instance, we don't really want a third-party login blocker to be installed, since it would never be used. I've been trying to come up with alternatives, but I don't really like anything I've come up with. Is there a better option that keeps code DRY that I'm missing? Thanks. tj -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/Njs9kLgbnHwJ. 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.
