On Fri, May 9, 2008 at 2:17 AM, Dan Price <[EMAIL PROTECTED]> wrote: > However, I've been thinking that an even more RESTful implementation is > possible-- we could avoid POST entirely, and use GET; for example: > > GET /filelist/0/SUNWgnome-img-editor-help-es/0.5.11%2C5.11-0.86/all > ^^^ ^^^^ > > This could mean: get all files associated with this package (this is the > "install fresh" case). This could even be mapped as: > > GET /package/0/SUNWgnome-img-editor-help-es/0.5.11%2C5.11-0.86 > ^^^^^^^^ > > Note that this could then be served by an HTTP cache or even a > plain old apache instance, since we have effectively altered a > non-static request into a completely static one.
This part I agree with. I believe that being able to have a standard server handle pipeline requests for these files would be the way to go. > For the upgrade case, we're trying to be bandwidth efficient, and > so we avoid fetching whole packages. In that case, the client could > either do the individual GETs, or ask a smart server for a specific list > of files in a RESTful way: > > GET /filelist/0/SUNWgnome-img-editor-help-es/0.5.11%2C5.11-0.86/1:2:7:9 > ^^^^^^^ > > This could mean "get the files associated with the 1st, 2nd, 7th, 9th > file actions in the manifest" (this would rely on the client and server > both obeying a predictable sort order for files in a manifest). I'm not keen on position-based requests. In my view, it is too opaque while monitoring the process and it seems error-prone. I would like to avoid sorting wherever possible. -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
