Dave Miner wrote:
> Knowing nothing about the WPAD method, I'm still bothered by the above;
> NWAM should not be in the business of responding to DHCPINFORM requests,
> because then you're trying to hijack DHCP server operations, which of
> course creates yet more problems. So can you clarify what you really mean?
It is not really hijack because if NWAM finds that the network
environment supports WPAD, it will not do anything. NWAM
does WPAD in the configuration process. If the environment
does not support WPAD, then NWAM will "provide" the info based
on the configuration set up by the sys admin, if it is
available.
This is just one proposal to make WPAD aware apps work with
NWAM without code changing. If people have other suggestions,
please post them. This will help us a lot.
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
