I am just starting module programming for Anope, so I am by no means versed in it. But I did have an idea for modules.
I know that the core Anope has functions for opening, closing, and manipulating .db files that should be used with Anope (nick.db, chan.db, oper.db, etc). I must say I was disappointed that there isn't a module API for this.
I believe it would be better to provide an API for this rather than making each module handle the situation on their own. Point in case, hs_request.c in the src/modules dir. It uses its own .db, which is clearly related to Anope, but it has to do its own leg work. This ultimately leads to duplicate code in the modules (to an extent) due to each module having to do the same things over and over. A module API for this would not only eliminate this duplicate code, it would (most likely) improve performance for modules, as all .db access/manipulations would come from the same source which could control read/write access and file locking.
Vadtec