You can certainly hide this additional complexity with your application either using Django as a pass through or configuring up something with a reverse proxy in Apache or such. There's no reason that I can think of that the complexity of maintaining a queueing system for asynchronous processing would need to be passed outward to a user.
If you want to give the user feedback on what's happening, you might consider maintaining a state message like "in progress" or such within Django that can be polled via an Ajax call or the like. -joe On Wed, Mar 26, 2008 at 9:07 AM, shabda <[EMAIL PROTECTED]> wrote: > > Not the end user but the people who would be downloading this > application, and want to use this, in a shared hosting environment. > > > On Mar 26, 7:39 pm, "Ian Lawrence" <[EMAIL PROTECTED]> wrote: > > Hi > > > > > are django and apache. Adding a HTTP server or configuring django- > > > queuing is too painful for the average user. :( > > > > what does the end user have to do with this? > > you have a server by doing > > wgethttp://svn.cherrypy.org/trunk/cherrypy/wsgiserver/__init__.py-O > > wsgiserver.py > > and setting up xml-rpc is not much more than this...i did this recently > athttps://help.ubuntu.com/community/UMEGuide/ApplicationDevelopment/GPS... > > > > and it is pretty simple to do (and really the best way IMO to run > > background processes) > > > > Ian > > > > --http://ianlawrence.info > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
