Shawn Walker wrote:
> On Mon, May 12, 2008 at 7:08 PM, Jordan Brown (Sun)
> <[EMAIL PROTECTED]> wrote:
>> Would this process involve listening on a network or local port?  In other
>> words, is the depot server started a general purpose server, or is it in
>> some fashion tied tightly to the requester (like talking via a pipe instead
>> of a TCP connection)?
> 
> For my prototype hack, it would have to be a tcp connection since
> that's how the depot server communicates.
> 
>>  Opening up a listening socket, even a local one, is security-impolite.
> 
> This is really just a prototype, and yes, I agree it is security-impolite.
> 
>>  It also sounds kind of inefficient, moving all those bytes through an
>> "extra" process and some kind of IPC.
> 
> Yes, but it does allow re-use of all of the existing depot code.
> 
> I was discussing the "no on-disk package format" with Stephen and Bart
> at Community One.
> 
> I'm just trying to get a better feel for what some of the ideas have been.
> 

One of the approaches I've been musing about is to abstract the depot
<> client communications more completely....   the goals would be as 
follows:

0) facilitate mirroring by allowing catalogs, manifests and files to come
from different sources.  By signing the catalogs and manifests, content
can come from anywhere.

1) make downloaded files usable between pkg invocations; when your wireless
craps out 450 MB into a large update, it's kind of frustrating that you have
to start from the beginning.   Also, installing multiple zones means a local
cache is a good idea...

2) enable the use of alternate transports, such as multicast, local mirror,
BitTorrent, DVDs, USB sticks, etc.

3) improve the asynchronous nature of pkg install by queuing download/
uncompression and verification of received content.

- Bart


-- 
Bart Smaalders                  Solaris Kernel Performance
[EMAIL PROTECTED]               http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to