[Bug 681] Handlers filenames and syntax versions

Neven Has haski at sezampro.yu
Tue Sep 30 05:26:24 PDT 2003

On Thu, Sep 25, 2003 at 09:32:26AM -0700, Kevin P. Fleming wrote:
> Here's what I've been thinking... instead of having a single set of 
> handler definition variables in the handler object, instead it could 
> define an array of definitions (each one being a structure), each with 
> a name/version/parameters/etc. combination, and a pointer (or 
> pointers) to the function that should be called to process that 
> specific combination. Then the nALFS core sees it as a series of 
> handlers, even though they all come from the same object file. The 
> core can then continue to call the correct one and the handler doesn't 
> actually have to have any code to check what version is being requested.

Sounds good.  There are a few functions in handlers that are used by
main code to get some handler-specific information (see
handler_alloc_execute_command() in execute.c for example).  Those
would have to be stored in the structure too.  I'm still not sure
what would be the best way to do that, as some handlers can (and do)
have more than one of those.


More information about the alfs-log mailing list