problems with TUX_ACTION_FINISH_REQ?

does anyone know of any problems or bugs with using TUX_ACTION_FINISH_REQ
in a tux module? i'm calling this within a module to take advantage
of http/1.1 keep alive connections. but when the same client goes
to make another request that *isn't* a request to the module, the
99% CPU problem happens immediately.

in other words, it seems that TUX_ACTION_FINISH_REQ doesn't work. and
yes, i'm running the latest tux kernel patch and userland rpm. :)

so, i'm going to use TUX_ACTION_FINISH_CLOSE_REQ instead. which is
too bad. does anyone who works on the tux source read this list?

-- 

steve simitzis : /sim' - i - jees/
          pala : saturn5 productions
 www.steve.org : 415.282.9979
  hath the daemon spawn no fire?