[Rubygems-developers] Roadmap for version 0.8.12

Hugh Sasse hgs at dmu.ac.uk
Tue Jul 19 06:47:02 EDT 2005


On Mon, 18 Jul 2005, Tom Copeland wrote:

> On Mon, 2005-07-18 at 07:46 -0400, Chad Fowler wrote:
>> I don't see a reason.  The non-compressed yaml index is only still
>> there to support old clients.  We could probably kill it at this
         [...]
>>
>> Tom, are you capturing user agent yet in Apache?  We send the
>> rubygems version as part of user agent, so we could look at this and
>> see what's hitting /yaml directly.
>
> Hm, I haven't been... but now we are; I just turned "combined" logging
> format for that vhost.  Here's the first couple dozen requests, mostly
> from RubyGems 0.8.11:
>
> ==============================
> 206.228.241.250 - - [18/Jul/2005:08:53:30 -0400] "HEAD /yaml HTTP/1.1"
> 200 0 "-" "-"
> 218.219.149.62 - - [18/Jul/2005:08:53:36 -0400]
> "GET /gems/rails-0.13.1.gem HTTP/1.1" 200 86016 "-" "RubyGems/0.8.11"
> 206.228.241.250 - - [18/Jul/2005:08:53:36 -0400]
> "GET /gems/sqlite3-ruby-1.1.0.gem HTTP/1.1" 200 39424 "-"
> "RubyGems/0.8.11"
> 218.219.149.62 - - [18/Jul/2005:08:53:45 -0400] "HEAD /yaml HTTP/1.1"
> 200 0 "-" "-"
         [...]

Rubygems doesn't seem to utilize the accept-encoding header -- it
doesn't show here and doesn't seem to be in the sources...

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.3

which may help, and covers my other point about only keeping one
form on the server, and deriving the other forms when needed.

         Hugh


More information about the Rubygems-developers mailing list