Hi, Excellent, a 0.3 release would also be really useful for us too.
I would suggest doing a release sooner rather than later, what other implementation tasks are there from your side that would need to be done before 0.3? Cheers, Gav On 20 Mar 2014, at 07:58, Gross, Lukas <[email protected]> wrote: > Hi, > > I agree that it would be more consistent to have only the request object > to cancel a request. I will change our code to use the request objects > cancel method and then remove the stop parameter from the library. > > We had problems using Google hangout in the past, however we could give it > another try. Just let me know when you have setup the branch and we can > schedule a session. > > We should also discuss the timeframe for the upcoming implementation tasks > so that we can plan the Objective CMIS 0.3 release. We need this new > release as early as possible so that we can get an approval for it :) > > Regards, > Lukas > > On 3/19/14 10:21 PM, "Gavin Cornwell" <[email protected]> wrote: > >> Hi, >> >> I do see your point about the stop parameter being a common paradigm in >> iOS, however, personally I would prefer that we remove it, especially if >> the request approach works. We then have one consistent way to cancel >> operations across the whole library (the parameter approach is only >> applicable to methods with progress). >> >> Great to hear you're also interested in the browser binding. I did my >> initial work a while ago so I need to sync it with the recent changes but >> I'll commit it in a branch as soon as I can. >> >> I too think it would be a great idea to resurrect the status meeting, >> even if it's just once a month. I will schedule something once I've >> committed something. Can you remind me, are you guys able to use Google >> Hangouts or would webex be a better choice? >> >> Regards, >> >> Gavin >
