File CRUD operations

* File create, delete, and get added.
* #get still needs a way to get the body and metadata at the same
   time. But also other response headers. May need a separate object for
   this–possibly a library-specific response object
* Not pleased with how Client#request is growing in complexity to handle
  various edges. More abstraction needed there.
Agreed. Wish it weren't necessary. Odd...

On Thu, Jul 31, 2014 at 3:16 PM, Ash Wilson <notifications@github.com>
wrote:

>> +        client.request(
>> +          method:   :head,
>> +          path:     "#{container_name}/#{name}",
>> +          expected: 200
>> +        )
>> +      )
>> +    end
>> +
>> +    docs "http://docs.rackspace.com/files/api/v1/cf-devguide/content/POST_updateaobjmeta_v1__account___container___object__objectServicesOperations_d1e000.html"
>> +    # This is both a delete and update operation. Metadata supplied as arguments
>> +    # to this method replace whatever metadata may already exist on a File.
>> +    # Be aware that this is significantly different from 
>> +    # {Container::update_metadata}.
>> +    # @param name [String] Name of the container to update metadata on
>> +    # @param args [Hash] Key-values to set as metadata on this object.
>> +    def replace_metadata(container_name, name, args = {})
> :+1: on using a different name for this operation than the Container one. It highlights the differences in API and is descriptive.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/elight/redrax/pull/7/files#r15663278