I've used Django as a web-service server. Still using HTTP, but with XML (sometime SOAP, but mainly custom dialects).
I've then built other front-ends onto this using GUI technologies, rather than web-based. Its something I fell into from neccesity, but has been a practical and efficient way to work. In my experience everybody want to separate presentation and logic, but developing a GUI application the two become to some extent intricately entwined. I've found using django for services, and a separate GUI client quite efficient. I might consider using the database API on its own in an application. But separating the components in the django code-base requires some effort. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
