In my case, it's quite urgent (it must work today), so do you have any example to execute this external script? Is it simple python (*.py) files? I was reading the link you sent, it's really interesting and it could be useful in a visual progress process, I will try it with another project.
Thanks in advance, 4nderson On 3/30/07, Atilla <[EMAIL PROTECTED]> wrote: > > Well, one thing that you could do is to execute an external script > from your view. Then you'd immediatelly return from the view, and the > script could mail them in the background. That is, of course, if you > don't need any feedback to be displayed. > > If you do need to do something like that, you'll need to make your > view provide some output every once in a while, so your webserver does > not time it out. However - that would cause your view to return data > to the browser quite slow. If you want it more interactive, you could > make the view generate output to a page with something AJAX-y, instead > of a normal web page. > http://my.opera.com/WebApplications/blog/show.dml/438711 - this idea > is quite nice, although I guess you don't need anything so flashy in > your case. > > > On 30/03/07, Anderson Santos Silva <[EMAIL PROTECTED]> wrote: > > > > That's exactly what I thought when I dealed with that, but I can't > > imagine a separated process running in the background and return a > > response to the user that his "action" was activated if every method > > waits to get back instead of a kind of thread operation. (Yes, I came > > from windows programming {delphi} to Web, so my knowledge is kind of > > limited with Python) > > > > Any suggestion? > > > > > > > > > > Atilla wrote: > > > Hello, > > > > > > By the looks of it, mod_fcgi has a limit as to how much time it could > > > wait for response from a script. Since you're doing a heavy operation > > > that takes a while, i guess it times out. > > > > > > The point is - if your executed action takes so much time, you're > > > clearly having a wrong conception on when and how you should be > > > executing it. It could be better off as an external process (that > > > still uses django in its code) that is triggered by certain actions in > > > your web-application, or scheduled by cron. In any case - it is not > > > the job of your django view to handle bulk transfers, it was not meant > > > to be doing that, even if the mod_fcgi didn't have the timeout. > > > > > > > > > On 30/03/07, Anderson Santos Silva <[EMAIL PROTECTED]> wrote: > > > > > >> Hello, I have a process that sends an e-mail to more then 5000 addresses > > >> (grouping it in 50 each time) and after a while it gives me the error: > > >> > > >> ------- > > >> Internal Server Error > > >> > > >> The server encountered an internal error or misconfiguration and was > > >> unable to complete your request. > > >> > > >> Please contact the server administrator, [EMAIL PROTECTED] and > > >> inform them of the time the error occurred, and anything you might have > > >> done that may have caused the error. > > >> > > >> More information about this error may be available in the server error > > >> log. > > >> > > >> Additionally, a 404 Not Found error was encountered while trying to use > > >> an ErrorDocument to handle the request. > > >> > > >> > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
