Hi I've found the issue causing tcp nodelay to fail on some connections in my fastcgi plugin. The issue is unrelated tho the flag itself.
If _mkp_event_read is called on a plugin created connection and returns MK_PLUGIN_RET_EVENT_CONTINUE while there is still data to be read (no 0 or -1 returned from call). The mk_conn_read function will check if a http session exists on this thread and create one if it does not. Because my connection is a unix socket, I get the tcp nodelay warning and a timeout on request because the epoll event is changed. Is this expected behavior? Should not MK_PLUGIN_RET_EVENT_CONTINUE allow the event to stay inside the module? Current behavior is the same as if I'd return MK_PLUGIN_RET_EVENT_CONTINUE. The issue is resolved in the plugin by always returning MK_PLUGIN_RET_EVENT_OWNED. -- Sonny Karlsson _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
