On Thu, Jul 19, 2012 at 1:19 PM, Timo Teras <timo.teras at iki.fi> wrote: > > Solutions that come up to my mind: > > - if the pool is deleted, the destructor should wait synchronously that > each cancel notification is received before continuing > > - or async version: increase pool refcount everytime async operation > is posted, and decrease it when an iocp notification is received > > - the OVERLAPPED structures *and* databuffers could be kept on separate > pool managed by ioqueue, so the memory will not get freed too early. > > Well I've figured what the alternative solutions are, it's just that I don't find them simple to implement. Benny -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120719/6d8f08ae/attachment.html>
