From: Danny G. <da...@ab...> - 2013-11-12 21:50:53
|
Sometimes you it's better to make breaking changes than to live with the mess that results from trying to be too accommodating. I say fix it right. Danny Gorton II Co-founder Absolute Power and Control, LLC www.absolutepowerandcontrol.com 517-499-9069 (mobile) On 11/12/2013 10:07 AM, Jiri Cincura wrote: > Hi *, > > I found a bug in connection pool. I *don't* know the root cause. But > anyway I think the code there isn't "good" or "nice", so to speak. But > I currently have an application in front of me, that escalates the > problem, some memory leaks. I think I might go to rewrite the pooling > (I implemented one earlier this year for another provider) and test > it. Hopefully it will be simpler, faster and correct. BUT it might > (will) not have exactly same API/behavior as the old one (and I don't > wanna to try mimic it). So it will be huge breaking change if you rely > on something like that. Of course the major version number will be > incremented. And I hope I'll not introduce more bugs. ;) > > Is there anybody against it? > |