On 7/12/07, Patrick <[EMAIL PROTECTED]> wrote: > Using a database is assumed,
Not true. URL dispatch, forms, and views still work. It very must depends what kind of site you're making. Though I raise my eyebrow at the idea that making something accessible via web service somehow makes it more secure than, say, a bog-standard secure DB connection. >and if I removed it from the picture, I'd > need to write a lot of code and probably use SOAP, XML or JSON for data > transfer over the wire. soapy, simplejson. Do you need querying? They made databases for that, and made them accessible to Internet Services. They're the new hot thing. ;-) > "Newforms" library seems flexible, but how feasible is it without > instances of a model and a database? Yep, you can use them without HTML, too. What would you do with the resulting data? Are you asking for a web-service backed Model? If so, using your own service protocol avoids the common ground upon which it could be built. I hear there's a SoC to do REST stuff. Maybe this would help: http://www.amazon.com/RESTful-Web-Services-Leonard-Richardson/dp/0596529260 You could use HTTPS with digest auth... > Is it even worth considering or are there better alternatives than Django > for this type of a web application? I dunno what kind of web application this is. :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
