Tom Mueller (pkg-discuss) wrote: > Shawn, > How about if we consider the questions that we want to be able to answer > using this data? > > - How many people have installed package such and such? > - How many people have updated package such and such to a new version? > -- How many of those were a specific request to update that package? > -- How many were part of an overall image-update? > - How many people have looked at information about a package? > > To answer these questions, it really isn't necessary to send the command > that triggered the operation, a transaction id. Also, if a client is > installing hundreds of packages, then there will be hundreds of requests > for manifests (with a little bit of information on each one). > I'd like to suggest that we return to Stephen's original proposal of > just sending the intent information: > > install/null > install/[previous_version] > info > contents > image-update/[previous_version] > > In the header of the manifest request. This allows us to answer the > questions above.
Tom, there are two problems with that: 1) The client could already have the manifests cached, which means I have to artificially perform a head request for each manifest. Performing a single POST or sending headers with all the information one time seems far more efficient than performing a HEAD for every single manifest the client will need. 2) The URI approach is not RESTful and won't work later with the "HTTP server" approach. Headers should work with most servers, and POSTs should be ignored by those that don't or throw back an error we can ignore. Whereas stuffing the URI chock-full of information will cause problems. Anyway, I as I responded to j earlier, I'm going to try to stick with the headers approach for now and if it creates problems, then I'll try something else. Cheers, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
