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

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
1acf54968533c93fdd5b7fe0d67a029c?d=identicon&s=25 Christopher Smith (Guest)
on 2009-05-25 22:59
(Received via mailing list)
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
1cfe895a7dd828f3dba77a8bc837d693?d=identicon&s=25 Avleen Vig (Guest)
on 2009-05-26 00:56
(Received via mailing list)
*wave*
1cfe895a7dd828f3dba77a8bc837d693?d=identicon&s=25 Avleen Vig (Guest)
on 2009-05-26 00:59
(Received via mailing list)
Hm, my apologies.
I need to learn to send replies to *individuals*.
Not to full lists.

:-)
This topic is locked and can not be replied to.