Stephen Hahn wrote: > * Shawn Walker <[EMAIL PROTECTED]> [2008-09-17 22:32]: >> Right now, I'm thinking of sending the history start_state to the server >> as that will tell us what the client is installing for the first time or >> what they're upgrading from and upgrading to. I could also send along >> the command that triggered it, the name of the operation (as perceived >> by the client) and eventually a transaction id (that could be used to >> help link error log entries to client tracebacks). > > No, no, and no: I already know which subset of operations from the > User-Agent and the intent, I can calculate the transaction from > correlations in time and location, and whether or not a set of > interactions happen because of overlapping client invocations isn't > relevant to the analysis. The RFE is use HEAD when the correct > manifest is already cached, with the original embed-in-URL approach > being refined to a embed-in-a-header approach. Does HEAD not > pipeline?
Yes, HEADs *should* pipeline according to rfc2616 [1]. Sorry, I was thinking of where we are now: all of our requests aren't pipelined. -- Shawn Walker [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
