RE: Next release (propose child interface change)

["Pill, Juergen" <Ju...@softwareag.com>]

Hello,

I want to suggest an API change in the child stores before we go into final
release (we talked about this some time ago).

Currently the security and lock child stores receive the uri (and the
permission/lock) as parameter only, but not the revisionNumber. This leads
to the fact, that Slide can lock only all versions or all versions are
unlocked (same applies for security, different versions of a resource may
not have a different set of permissions). If we would extend those
interfaces with the revisionNumber/revisionDescriptor, different versions of
a resource may be locked by diffferent idividuals and some versions may not
be locked at all.

What do you think? Do you want me to change these interfaces and modify the
Slide layer accordingly next week?

Best regards

Juergen Pill


 

-----Original Message-----
From: Remy Maucherat [mailto:remm@apache.org]
Sent: Friday, May 04, 2001 1:53 AM
To: slide-dev@jakarta.apache.org
Subject: Re: Next release


> I'll try and get the important change to you by Saturday.
>
> Not to start a long discussion, but what's the policy with respect to
> changing interfaces after they're published?  I tend to lean towards the
> "interfaces are immutable, after they're published they may not be
changed"
> policy.
>
> But I realize the definition of "published" is different for Open Source
> software.

Yes, I also think that incompatible API changes must be avoided at all
costs.
Of course, if it turns out there's something really broken, it has to be
changed (that happened some time ago with the transaction related API, and
more recently with the split of the WebDAV client library).

> Anyway, I mainly wanted to clean up the interface before it got exposed to
> the public.

No problem.

Remy