Shawn Walker wrote: > I've asked Danek to respond to this, but here's my primary issue: > > * I don't believe that most users are going to want to manage multiple > versions of the same origin > > That is, I don't believe it's useful to support multiple proxies for a > single origin, and even if we can, I don't think the user wants to manage > each one of those as separate origins.
In the meeting, Bart brought up the canonical use case: a laptop that moves between a proxied environment (inside) and a non-proxied environment (outside), and wants to access external origins from both environments. This would be very nice for Oracle folks who have homeunix.com or whatever configured. It probably wouldn't matter for anyone whose company didn't have a firewall policy from 1995. I think given that we don't expect many people to use this, we shouldn't expect many people to get confused by this. Fixed machines almost certainly won't have any origins with more than one proxy, assuming they have any proxy needs at all, and that probably covers 99% of our customer base. And I'd guess that even for mobile machines, this is highly unlikely to be used. But the complexity isn't ridiculous, and the flexibility allows those few folks to do what they need. We would need to make sure that any other metadata associated with origins isn't added orthogonally to proxies -- that is, you shouldn't have to name the full tuple of an origin's metadata in order to refer to it. That suggests that users might need a way to name the configured origins. Right now, that's effectively its proxy, but that's not a good handle going forward. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
