Comments on: Media Types, Plumbing and Democracy http://www.subbu.org/blog/2009/12/media-types-and-plumbing Wed, 08 Feb 2012 05:16:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Gregg Caines (@GreggCaines) http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-169446 Gregg Caines (@GreggCaines) Sun, 25 Sep 2011 01:54:26 +0000 http://www.subbu.org/?p=1024#comment-169446 @steveklabnik Enjoyed your #twiliocon talk! What's your take on the "conneg != versioning" argument, ie: http://t.co/QqK9ht1q ? @steveklabnik Enjoyed your #twiliocon talk! What’s your take on the "conneg != versioning" argument, ie: http://t.co/QqK9ht1q ?

]]> By: Jeremy Brown (@notmessenger) http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-127667 Jeremy Brown (@notmessenger) Thu, 17 Mar 2011 02:50:36 +0000 http://www.subbu.org/?p=1024#comment-127667 I have weighed in on this subject with an opinion of my own, but my response is much longer than what is warranted for this comment section. I have written up my opinion and published it on my blog at http://www.notmessenger.com/rest/3-tenets-for-implementing-a-rest-api/ This is not an attempt to get traffic to my blog or a spam message, but merely an attempt to add my opinion to the conversation. Thank you for time. I have weighed in on this subject with an opinion of my own, but my response is much longer than what is warranted for this comment section. I have written up my opinion and published it on my blog at http://www.notmessenger.com/rest/3-tenets-for-implementing-a-rest-api/ This is not an attempt to get traffic to my blog or a spam message, but merely an attempt to add my opinion to the conversation. Thank you for time.

]]> By: 3 tenets for implementing a REST API « Notmessenger's messages http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-127630 3 tenets for implementing a REST API « Notmessenger's messages Wed, 16 Mar 2011 21:55:58 +0000 http://www.subbu.org/?p=1024#comment-127630 [...] http://www.subbu.org/blog/2009/12/media-types-and-plumbing [...] [...] http://www.subbu.org/blog/2009/12/media-types-and-plumbing [...]

]]> By: 3 tenants for implementing a REST API « Notmessenger's messages http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-127628 3 tenants for implementing a REST API « Notmessenger's messages Wed, 16 Mar 2011 21:44:03 +0000 http://www.subbu.org/?p=1024#comment-127628 [...] http://www.subbu.org/blog/2009/12/media-types-and-plumbing [...] [...] http://www.subbu.org/blog/2009/12/media-types-and-plumbing [...]

]]> By: Colin Jack http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-76663 Colin Jack Tue, 29 Jun 2010 20:14:35 +0000 http://www.subbu.org/?p=1024#comment-76663 "version of the business logic involved in “accessing” PO/123" Why would a client care what version of the business logic (code?) was used? “version of the business logic involved in “accessing” PO/123″

Why would a client care what version of the business logic (code?) was used?

]]> By: Colin Jack http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-76660 Colin Jack Tue, 29 Jun 2010 20:09:55 +0000 http://www.subbu.org/?p=1024#comment-76660 "However, as an intermediate step, perhaps it would be useful to produce a “Media Types Design Best Practices” document(/blog/forum ???) where we can hash out how to be a good media type citizen." Great idea, did it go anywhere? “However, as an intermediate step, perhaps it would be useful to produce a “Media Types Design Best Practices” document(/blog/forum ???) where we can hash out how to be a good media type citizen.”

Great idea, did it go anywhere?

]]> By: subbu http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-50271 subbu Wed, 13 Jan 2010 18:08:08 +0000 http://www.subbu.org/?p=1024#comment-50271 Once the message gets into the app runtime (e.g. JAX-RS) routing is not a big problem, but I am talking about the message routing from the time it reaches some front-end proxy till the time it is fed into a runtime. This gets more interesting when you consider homegrown/commercial CDNs setup with origin servers half-way across the globe. When developers make choices about URIs and media types, they must not ignore these situations. These are more real, and in some cases, more important than application level considerations. Once the message gets into the app runtime (e.g. JAX-RS) routing is not a big problem, but I am talking about the message routing from the time it reaches some front-end proxy till the time it is fed into a runtime. This gets more interesting when you consider homegrown/commercial CDNs setup with origin servers half-way across the globe. When developers make choices about URIs and media types, they must not ignore these situations. These are more real, and in some cases, more important than application level considerations.

]]> By: Bill Burke http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-50253 Bill Burke Wed, 13 Jan 2010 14:01:01 +0000 http://www.subbu.org/?p=1024#comment-50253 JAX-RS can route based on media type. That is not the problem. The problem resides in the fact that most (all?) JAX-RS implementations are built on top of a servlet container. Each web deployment is its own classloader and thus you can't version classes within it. I don't know of any servlet implementations that allow you to bind different web deployments to the same URL scheme. JAX-RS can route based on media type. That is not the problem. The problem resides in the fact that most (all?) JAX-RS implementations are built on top of a servlet container. Each web deployment is its own classloader and thus you can’t version classes within it. I don’t know of any servlet implementations that allow you to bind different web deployments to the same URL scheme.

]]> By: subbu http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-50196 subbu Tue, 12 Jan 2010 22:52:29 +0000 http://www.subbu.org/?p=1024#comment-50196 <blockquote> In Java land, with the current tools available, it would be very hard to implement a common URL scheme that served up different versions of the same application using conneg. </blockquote> This is exactly the problem I was referring to in my comment about routing rules.

In Java land, with the current tools available, it would be very hard to implement a common URL scheme that served up different versions of the same application using conneg.

This is exactly the problem I was referring to in my comment about routing rules.

]]> By: Bill Burke http://www.subbu.org/blog/2009/12/media-types-and-plumbing/comment-page-1#comment-50195 Bill Burke Tue, 12 Jan 2010 22:43:24 +0000 http://www.subbu.org/?p=1024#comment-50195 I don't think your PO/Album example is a good one. A better one would be an Oracle Financials PO vs. a SAP PO. Or a Saleforce.com contact vs. a Thunderbird contact. If a client receives a URL how is it supposed to ask for, or find out a specific XML format exists? Conneg + custom media types is one way. Links are another. One causes an explosion of media types, the other an explosion of links. no? I don't have time now, but I'll blog more about what I mean by this. As for versioning, I was all for using a version tag within a media type along with conneg. Now, I'm not so sure, but, not because of this blog post. In Java land, with the current tools available, it would be very hard to implement a common URL scheme that served up different versions of the same application using conneg. The problem being that you'll probably have different versions of the same Java class that process this data. Using hateoas pretty much can hide any complicated URL scheme that proliferates because of applicationv versioning. I don’t think your PO/Album example is a good one. A better one would be an Oracle Financials PO vs. a SAP PO. Or a Saleforce.com contact vs. a Thunderbird contact. If a client receives a URL how is it supposed to ask for, or find out a specific XML format exists? Conneg + custom media types is one way. Links are another. One causes an explosion of media types, the other an explosion of links. no? I don’t have time now, but I’ll blog more about what I mean by this.

As for versioning, I was all for using a version tag within a media type along with conneg. Now, I’m not so sure, but, not because of this blog post. In Java land, with the current tools available, it would be very hard to implement a common URL scheme that served up different versions of the same application using conneg. The problem being that you’ll probably have different versions of the same Java class that process this data. Using hateoas pretty much can hide any complicated URL scheme that proliferates because of applicationv versioning.

]]>