----- Oryginalna wiadomość -----
> Od: "Roberto De Ioris" <[email protected]>
> Do: "uWSGI developers and users list" <[email protected]>
> Wysłane: środa, 11 styczeń 2012 11:17:26
> Temat: Re: [uWSGI] after req hook
>
> you have put a sleep in the request handler, not in the
> after_req_hook.
>
> harakiri will be always available for request handler, will be
> disabled in after_req_hook on demand
>
Clear :]
I understand the idea of no-harakiri-arh a little differently, but is OK.
Would it be a big problem to call after_req_hook after the signal?
eg.
import time
import uwsgi
def application(env, start_response):
start_response('200 OK', [('Content-Type', 'text/html')])
yield b"ok"
def after_req():
print('************* after_req')
uwsgi.after_req_hook = after_req
def timer(id):
print('************* timer start')
#time.sleep(10)
raise Exception('yyy')
print('************* timer end')
uwsgi.register_signal(1, "worker", timer)
uwsgi.add_timer(1, 5)
I would like to "after_req" was executed after "timer".
--
Łukasz Wróblewski
http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe
http://www.hostowisko.pl/ - Profesjonalny i tani hosting
http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
