Hi, I understand the suggestion and it does make sense, as do the other that have been suggested. However, I am thinking about the following issues:
1. The data that I am consuming (XML) is a pretty complex structure. I want to convert it to a Python structure that I can pass to Django templates. 2. If I convert data in just another format that still needs to be converted to Python structures I am somewhat more advanced but still not in a perfect situation. 3. I would like my Python data to be available to Django on every web request without me having to check on the local disk if a file has changed, etc. This is why I have been thinking about another thread that would just update data when required and structures would be available to Django immediately. Also do note that I am in the process of evaluating Django for its abilities to integrate with other external services. This is the reason why I am trying to get to the most optimal way to achieve things with Django. In the particular problem that I have to solve right now I could be happy with one of the fore-mentioned solutions, but I do have a strong interest in finding out how to integrate Django in a more complex set-up. Thanks a lot for taking the time to help me through this, Paul Adrian Holovaty wrote: [...] > I'd suggest having a separate script, independent of Web requests, > that grabs the XML and formats it once a minute. Then just point > Django at that already-formatted data and present it. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
