On Wed, Jun 02, 2010 at 04:25:46PM -0700, Edward Pilatowicz wrote:
> On Wed, Jun 02, 2010 at 03:39:02PM -0700, Nicolas Williams wrote:
> > On Wed, Jun 02, 2010 at 03:36:14PM -0700, Edward Pilatowicz wrote:
> > > the system repo is a requirement for secure zones upgrade.
> > > theoretically the system repo could run over any transport, but domain
> > > sockets is a natural choice for supporting zones since it doesn't make
> > > any assumptions about the network configuration associated with zones.
> > > (scratch zones have no networking, and there's no guarantee that regular
> > > zones will have network access to the global zone.)
> >
> > Maybe we need HTTP-over-doors...
> >
> > (Says I only half-jokingly, but with tongue firmly in cheek.)
>
> hey, that would allow us to do easy http access from within the kernel.
> i can just imagine:
> modload("http://kernel.org/snv_140/kernel/drv/ramdisk";)
>
> oops. i think i just poked a hole in the side of my face.
well, I didn't mean that the door HTTP server would be a proxy... I'm
not sure how you'd write HTTP URIs over doors...
More seriously, how would you write HTTP URIs over Unix domain sockets?
http:///path-to-socket/resource/path? But how would you distinguish the
path to the socket from the path to the resource?? Or maybe just
http:///resource/path (the path to the socket would be implied, and
there could be only one).
Presumably only the IPS stack would understand such URIs...
Nico
--
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
