On Mon, 8 Oct 2001, Dossy wrote: > On 2001.10.08, Tomasz Kosiak <[EMAIL PROTECTED]> wrote: > > I would like to use these mechanisms to allow independent TCL modules > > to handle parts of URL tree. During request handling I would like to > > identify which TCL module handles which url (exactly which instance of > > given module). > > Can you not register pretrace filters which would decide what > handler to invoke based on the criteria you're planning on > using?
Can you give me some more info on what you propose? I certainly don't want to use filters to handle requests because this is better done with Ns_RegisterRequest. I could try to use filters to identify the handler, but: - I will have to keep filters synchronized with hanlders, so when I register handler I would have to register filter to identify the hanlder - simple filter registration won't solve the problem of overlappping handlers (eg. /news* and /news/financial*) and I don't' want to create solution like ACS Request Processor. - I don't want do register filters for static content to avoid overhead of interpretor initialization and cleanup > That's how I've implemented CGI in AOLserver for the AOLserver > Wiki (instead of using nscgi). Could you be more verbose and draft your solution? Anyway I wonder what's was wrong with nscgi module that make you decide to implement CGI the other way. --tkosiak
