Webservice as a Stable API
jeffh at tragicallyleet.com
Tue Aug 22 06:55:27 UTC 2006
The way I have seen it handled elsewhere to change the url. For
then when we learn a bunch and want to change we move to v2. Support
one version back of the api as depricated and go from there.
On Aug 21, 2006, at 9:32 AM, Max Kanat-Alexander wrote:
> On Mon, 2006-08-21 at 10:15 +0100, Gervase Markham wrote:
>> On the same principle, should we make all return values hashes? Or is
>> that overkill?
> That seems like a good idea to me, too.
>>> 3) Functions don't disappear.
>> But if we end up with a big backwards-compatibility problem, we can
>> always add doFoo2().
> Good point.
>> I would hope everything is EXPERIMENTAL at the moment!
> It is. :-) Or its undocumented, which makes it UNSTABLE.
>>> Anything labeled "EXPERIMENTAL" should
>>> become "STABLE" by a final release.
>> I don't agree (reasonably strongly). This effectively makes all
>> interface stabilisation block the release. I think it's entirely
>> fine to
>> ship final releases with things still labelled EXPERIMENTAL. That
>> tells people not to use them if they want to be sure their code won't
>> break. We should not rush stabilisation of an interface.
> Okay, fair enough. Although I think release time is the time to
> *consider* stabilization. I think we should have some point where it's
> somewhat forced (or at least forced to be considered), since otherwise
> we could just gleefully mark everything EXPERIMENTAL forever and
> keep on
> changing it. :-)
> Competent, Friendly Bugzilla Services. And Everything Else, too.
> To view or change your list settings, click here:
More information about the developers