As part of the work I'm doing for bug 2022 "make manifest request provide more information for download tracking", it seems there is some overlap with some of the possible hooks we want to put into place for "verbose mode" or "debugging."
Specifically, I feel like my current solution for passing along the intent of the client's operation is hacky at best: http://cr.opensolaris.org/~swalker/pkg-2022/ It seems like there is an opportunity here with the work on debug / verbose to find a better way to pass around operational information than adding a parameter to a few dozen subroutines. Will the verbose / debugging information changes generate and store the information in an internal structure as we go along and then dump that information in a human-readable format at appropriate intervals? If so, that would allow the client to re-use that information to either make better decisions about operations or to provide that information to the server without requiring extensive alterations to our api internally. In my case, I need information about the operation that the client was performing at the time that a manifest is requested, so that I can tell the server *why* the client requested it. Particularly troublesome, to me at the moment, is how best to retrieve previous version information (if they're upgrading from an older package). Thoughts? -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
