[EMAIL PROTECTED] wrote: >> 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
It's not my preference to do this, certainly. But isn't there a size limit? How do I guarantee I'm not sending along a megabyte of text in the header? I'm concerned that this will cause problems. > future. How do you envision this working once we start sending our FILE > requests via pipelined http GETs? That was the other reason I asked... I'm concerned about header size. -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
