For 4, NWAM can probably do the following. NWAM can perform WPAD and check if there is proxy info available from any server (we need to figure out what to do if there are multiple servers providing different info). If the info is available, then NWAM may do nothing. A WPAD aware app will find the proper info from the server(s). But if there is no proxy info available from the server(s) and there is a NWAM proxy setting associated with the current network environment, NWAM may "fake" a DHCP server (*) reply using that info to any query done by WPAD aware apps. The WPAD aware app will take this info. If there is proxy info available from the server(s) and there is also a NWAM proxy setting, NWAM can still "fake" a DHCP server reply if the setting is supposed to override the proxy info from the server(s).
I would suggest not pursuing this whole contraption unless it proves to be impossible to move critical apps off of WPAD. Faking responses would seem to open up a whole set of headaches for marginal benefit. Coalescing apps around fewer mechanisms rather than encouraging duplicative ones seems like the better direction.
Dave _______________________________________________ networking-discuss mailing list [email protected]
