On 04/27/2010 09:26 AM, Devan Goodwin wrote:
The v2 in the URL is gross but it would help with keeping the code
reusable I think as we could fork to different resources inheriting
from common parent classes. Not sure if we could do the same with
media type checking, at least not as easily.
Well.. even with media-type=application/json+version2.0 we have issues
with code re-use and refactoring
Would the plain URL always be the latest and greatest with vX for
those who want stability? Or is it no vX assumed to be v1 and we
increment for all future releases.
No v would be v1. Think of V1 as the fifth column.
-- bk