Darren Reed wrote:
> Has the NWAM team looked at UPnP?
>
> http://www.upnp.org/
> And specific to this would be CR#6224486
>
> Or to have a better idea of what the "competition" does,
> plug in a Windows XP box to a LAN, snoop the traffic and
> toggle the "automatic discovery" for the proxy setting.
>
> You should see it broadcast looking for an http proxy.
I will check it out. Thanks.
> So how does this relate to what we should do with Solaris?
>
> *IF* you wanted to steer away from making something
> Solaris specific, I'd argue that one approach would be
> to adapt programs such as web browsers to send out a
> request for the http proxy on the loopback interface and
> for Solaris to provide a daemon that listens for and answers
> those queries with information provided to it via some
> "other means".
So this requires changing the apps, right? The obvious
problem is that we cannot change every apps. I suspect
that it may not even be possible to change the bundled
Firefox as this will cause the Sun code base to diverge
from the core one.
BTW, what does Firefox do when the proxy setting is set
to Auto-detect? Does it do the above?
> That "other means" could be broadcasting on the network
> itself, to find the answer, or reading data from a config
> file or using the GNOME interface.
>
> Another approach might be to just have applications use
> UPnP directly to the LAN, without having a middleware
> daemon run on Solaris.
>
> So some pros and cons with this approach:
> pro - it implements an "industry standard" protocol;
> con - it's not a simple solution;
I guess it is a solution for a bigger problem.
> pro - the work undertaken by Sun could be contributed
> back to the open source community;
> con - it requires changes to all programs that currently
> use proxies;
This is the key problem. Even if we contribute back to
the community, a lot of apps still may not be changed to
use it.
> pro - if a daemon is developed, we increase our position
> as a worthwhile platform in the network appliance
> space;
> ...and so on...
Note that we are also looking at other similar types
of technologies, like Bonjour.
> In addition, we could think about adding vendor specific
> type codes to DHCP for proxies (I'm surprised that there
> is nothing in DHCP for this - that I can find- yet) that
> are retrieved at bootup and fed into the GNOME thing or
> your login shell as $http_proxy, etc.
So this suggestion is about having a "default" environment
variable set for all processes after bootup. But how about
changing it after bootup? How about apps which do not
use this method to obtain proxy info?
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
