On Tuesday 12 July 2011 11:44:54 you wrote:
> On 12/07/11 19:15, Julian Edwards wrote:
> > We could, but I'd rather not have yet another method name when I want
> > synchronous copying to simply die.
> >
> > However, I think I have no choice as it doesn't look like we have a way
> > of figuring out the api version in use inside the method code.
>
> You export two Python methods under the same webservice name, but
> restrict them to disjoint sets of versions.
That was what I had feared.
> But you could possibly take this opportunity to rename it to something
> like 'copyPackage'.
I had considered that.
But then we'd have a syncSource() that copies packages, and a copyPackage()
that syncs sources.
On Tuesday 12 July 2011 11:44:54 you wrote:
> On 12/07/11 19:15, Julian Edwards wrote:
> > We could, but I'd rather not have yet another method name when I want
> > synchronous copying to simply die.
> >
> > However, I think I have no choice as it doesn't look like we have a way
> > of figuring out the api version in use inside the method code.
>
> You export two Python methods under the same webservice name, but
> restrict them to disjoint sets of versions.
That was what I had feared.
> But you could possibly take this opportunity to rename it to something
> like 'copyPackage'.
I had considered that.
But then we'd have a syncSource() that copies packages, and a copyPackage()
that syncs sources.
GNARGH.