openstack team mailing list archive

[Bryan Taylor <btaylor@xxxxxxxxxxxxx>]

It's true that HTTP assigns no meaning to the extension, but HTTP leaves 
it to the server to decide the meaning of its own resources and their 
location within its URI structure. The filename extension meme is 
extremely common for variant resources. We adopt these conventions only 
so that that our server code can easily figure out what to do and to 
promote what Fielding calls "serendipitous use" by our human clients 
(developers).


On 10/12/2011 02:00 PM, George Reese wrote:
> The extension has nothing to do with representation in HTTP. It's the content type (in the headers).
>
> Sent from my iPhone
>
> On Oct 12, 2011, at 17:15, Bryan Taylor<btaylor@xxxxxxxxxxxxx>  wrote:
>
> > On 10/11/2011 10:28 AM, George Reese wrote:
> > > It's wildly inappropriate to equate a thing with its representation.
> >
> > Unless the thing is itself a representation, yes. A resource can be ANYTHING: a server, a database record about a server, a car, a rock, the concept of love, the act of smiling, or a representation of a second resource, etc...
> >
> > http://example.com/thing is the thing
> > http://example.com/v1/thing is the set of v1 representation of the thing
> > http://example.com/v2/thing is the set of v2 representation of the thing
> > http://example.com/v1/thing.json is the v1 JSON representation of the thing
> > http://example.com/v2/thing.xml is the v2 XML representation of the thing
> >
> > A resource that represents a representation or set of representations of second resource is called a variant resource of the other.
> > This email may include confidential information. If you received it in error, please delete it.
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp