9 Dec
2008
9 Dec
'08
1:07 p.m.
Andrei Pelinescu-Onciul schrieb:
[crossposting since this is of general interest]
On Nov 12, 2008 at 00:30, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote:
Hi Andrei!
I wonder what happen if the asynchronous sending fails (e.g. TCP
connection is lost). Will it jump to failure route (for requests)? What
happens if the sending of the response (e.g. 200 ok) fails? Will acc
module account the failed 200 ok?
regards
klaus
Can this also be used for DNS lookups and TCP/TLS
connection setup?
Yes for DNS (see above) and in general for any route-level async processing
involving tm (e.g. lookup some part of the message in a slow DB and
execute automatically another route when the DB responds).
It cannot be used for TCP/TLS, but it's not needed anyway. In ser TCP
connection setup and TCP send is already asynchronous, at least if
you have tcp_buf_write=yes in ser.cfg (I agree it's not a very well
chosen name :-)). TLS does not support it yet, so if you use TLS