Paul Querna <[EMAIL PROTECTED]> wrote:
> Nope, mostly because with how the current API is structured, we don't
> know what module will handle the protocol until runtime. It could be
> one that wants Accept Filtering, or one that doesn't.
>
> If you could with 100% accuracy match a single Listener Record to a
> Single Protocol Module, then an API could be created to better handle
> this situation.
How about meeting you halfway: The "Listen" directive still needs a protocol
tag, that makes sense, and IMHO it actually reduces the need for comments in
the config file because when you look at the Listen directive you can tell
right away what it's there for. So say I did
Listen *:6669 bt_peer
Is there (or should there be) a way to hook in to do the equivalent of
"AcceptFilter bt_peer none" from C, after the configuration file has been
parsed?
Thanks,
Tyler
