> With this in mind, this seems like quite a bit of information to pass > along in the header. As such, I've been considering a separate POST > operation before the client fetches a manifest (regardless of cache > status), begins a filelist operation, etc. that provides this > information instead of trying to squeeze it into the headers.
This doesn't seem like a good idea. We're adding a second round-trip and connection setup / tear-down into the process of starting an operation. This is going to make these harder to streamline in the future. How do you envision this working once we start sending our FILE requests via pipelined http GETs? -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
