Bill de hÓra wrote: > I think you're making things complicated - you don't want to deal with a > database but do want to pass marshaled python structures into django > templates. Don't do an end run around the framework. The way to go > about this is to pull down the XML scheduled via cron or some other > timed process, marshall it to an object and save() that object into a > table. That way your django template/view code knows nothing about where > the objects are coming from, how they are constructed, or how often they > should check for freshness; and if this data is as complex as you say > marshalling and storing in another process seems sensible. > > cheers > Bill
I see. So I should use the database as the IPC mechanism to talk to Django. I am not certain, however, that I understand what you mean to save the object into a table. You mean something like "pickle"? So I wouldn't have to create the whole structure in the database but I would use a simple table to store something like a "blob" that is my latest object? Sorry if I misunderstood your suggestion. I do agree with the other comments, having a different process that takes care of where data is comming from. Regards, Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
