On 24 Apr 2009, at 10:55 , earcar wrote: > 1. We already have the URLs and XSDs for the REST interface, but the > first are quite different from a correct REST implementation (no GET / > person, but GET /getperson, and so on). Sooo... it's absolutely not REST, it's RPC.
> So the questions are: > 1. does Django support REST queries? I fear that question doesn't make any sense, REST is an architectural style, not a language or anything, there are no "REST queries". Other than that, yes you can make django understand remote procedure calls via URLs, there might even be third-party apps for that. I don't think Django has any "native" support for that though. > 2. is possible to do a Django application without db? Are there any > ORM things that will do the same job for XML data instead? If not, is > possible to do that for mere mortals (with xpath/dom/sax as the > preferred ways)? Where are you storing your XML data exactly? > 3. is possible for Django to validate the XML of every single REST > query (input and output) using XSD? Why wouldn't it be? > 4. is possible to render views using xslt? I think you mean templates here, in Django's lingo. Yes you can although it might not be the smartest idea ever, and you won't be able to use Django's template system > or better render in xml, Use Genshi as a template engine instead of django's template system. > leaving the xslt work to the browser? That's a bad idea. If only because not all browsers can do that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
