From: Intransition Date: 2012-08-07T23:47:23+09:00 Subject: Re: Supporting multiple versions of an API ------=_Part_1026_15842587.1344350841098 Content-Type: multipart/alternative; boundary="----=_Part_1027_11942175.1344350841098" ------=_Part_1027_11942175.1344350841098 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Thursday, August 2, 2012 5:16:34 PM UTC-4, Robert Klemme wrote: > > > So it's *not* the user deciding on the API version! That's a > different situation. Or does the user present the loaded YAML file? > Can you be a bit more specific about your usage scenario? > Well ultimately the user creates the files, in some fashion or another. So it just depends on how you look at it, I guess. I'll put a link to the project once it's a bit more settled. Right now the project is in the demonic throws of the Over-Thought. ------=_Part_1027_11942175.1344350841098 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On Thursday, August 2, 2012 5:16:34 PM UTC-4, Robert Klemme wrote:

So it's *not* the user deciding on the API version!  That's a
different situation.  Or does the user present the loaded YAML file?
Can you be a bit more specific about your usage scenario?

Well ultimately the user creates the files, in some fashion or another. So it just depends on how you look at it, I guess.

I'll put a link to the project once it's a bit more settled. Right now the project is in the demonic throws of the Over-Thought.

------=_Part_1027_11942175.1344350841098-- ------=_Part_1026_15842587.1344350841098--