Hooking in to the nginx event loop with something other than TCP?

[Christopher Smith]

I am trying to have a filter module that would query a UDP network 
service before altering the output of an HTTP request. If the service 
was TCP based, I can see how I'd do this without blocking the worker 
thread (the memcached module provides a great example). However, it 
seems like the API's for doing this assume that there is a TCP 
connection involved. It looks like I even nginx_epoll_add_event() uses 
ngx_connection_t, which appears to have some assumptions that it is 
working with a connection oriented socket, rather than a packet-based 
one. Is there a way to do this?

--Chris