Kannel & blocking connect again.

I want to discuss serious problem in Kannel WAP gateway.
It is about blocking connect(). Now any malicious user can
hang up kannel. It is too simple to do.
Anyone can send request from WAP phone to host which is configured
to drop SYN packets.

For example: after simple command (for 10.10.10.10 owners)
iptables -A INPUT -p tcp -d 10.10.10.10 --destination-port 8081 --syn -j DROP
any request to http:/10.10.10.10:8081/ will block kannel totally
(couse http.c blocks in connect()) and other requests will be timed out.

Kannel branch 0.12.* hasn't this problem couse in it every http request was
made by own thread.

So: to use current kannel version in comercial enviroment
(as _WAP_ gateway, not as _SMSC_ gateway) we need to implement nonblocking
connect first.
What people think about it?
Will kannel migrate to new internal architecture (from Kalle Marjola)
where nonblocking connect is implemented among the other futures?
Is it discussed already?

-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv