is there any reason you want to process the "webservices" on the server side? unless there is any special reason to do this, it looks like kind of redundant and actually that is one of the main reasons to use webservices (decentralized application model). that means you would want to spit out client side code that actually does the processing.
there are some situations where you want to "cache" a webservice, so the server would do the service "fetching". both approaches are easily done with django. On Mar 21, 2:04 pm, "Nathan Harmston" <[EMAIL PROTECTED]> wrote: > When I say Web Services, I am including SOAP aswell as REST. So my django > project actually becomes a portal to various web services hosted by external > entities. So is the best way to do it, to have a job model which holds the > various job data and have a process running which runs the web service and > updates the relevant job model so when the user views the "results" view it > appears properly. The view could return results if the result was retrieved > within a specific time period, else it would return a "work in progress". > Would this kind of thing work? So the "WS client process" and Django both > share the same models and "talk" using the database? Is there any problem > with this that anyone can see? > > Would this work? > > Many Thanks in advance, > > Nathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
