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?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
