6
Hi all
Catzwolf: I actually thought about a more elaborate method, but (imho) there are 2 ways of seeing this:
1- The hook is an integral part of the module, as such the module developer creates the hooks. Users can always customize them of course. One advantage of this is that, since the module creator knows every intricacy to his/her module, it's a lot easier for him to create these hooks.
2- The module data belongs to the site, as such should be accessed by the site, from any module. In theory this sounds like the better method but there are some drawbacks; what if data from the module isn't stored solely in DB? I've designed modules where part of the data is stored in an xml file. There's also the question of system resources, hooks, if not designed very carefully can bring a site with a lot of modules to it's knees.
My solution uses method 1.
Could there be a solution that uses the best of both methods?
www.kaotik.biz