Re: prompt_hook

When you say "existing functionality", you should note that the existing
net_*_filter hooks don't do what I intended them to do.  So I don't
consider them "existing functionality" but rather "broken things".  Same
thing with the telnet option hook--that's also broken.  In the case of all
three of those hooks, I'm not using them for what I originally wrote them
for.  So I figured I'd assess whether it makes sense to remove them.
That's what this conversation is about.

If you want an example of why I think it's broken, look at the MCCP plugin
I hobbled together.  It's a mess because I had to work around
implementation flaws in the existing net hooks.

If you can change your implementation to use something else (like the
mud_filter_hook), then we don't need to keep the net_*_filter hooks around
since as far as I know you're the only one using them.

In regards to MXP and MIP, both of those are just markup languages and I
think they can both be implemented at the mud_filter_hook level.  I'm not
sure why they would need to be implemented at the network level.

/will


On Tue, 20 Apr 2004, Chris Heilman wrote:
>
> I'm not remembering what the issue is, but it still seems strange to
> remove existing functionality from the client.  I refuse to believe that
> calling an empty hook is hurting performance.
>
> How would you implement something like the Portal MIP, or MXP?
>
> -Chris


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click