Hi David, >>>> If you plan to do a v14 for this API comment, I'm wondering if the >>>> documentation could be slightly modified too. I think "external mempool >>>> manager" was the legacy name for the feature, but maybe it could be >>>> changed in "alternative mempool handlers" or "changing the mempool >>>> handler". I mean the word "external" is probably not appropriate now, >>>> especially if we add other handlers in the mempool lib. >>>> >>>> My 2 cents, >>>> Olivier >>> I had not planned on doing another revision. And I think the term >>> "External >>> Mempool Manager" accurately describes the functionality, so I'd really >>> prefer to leave it as it is. >> I think there is no manager, just a default handler which can be changed. >> I agree the documentation must be fixed. > > OK, I have two suggestions to add into the mix. > 1. mempool handler framework > or simply > 2. mempool handlers. (the alternative is implied). "The mempool handler > feature", etc.
Option 2 is fine for me. Thanks!
