On Mon, May 19, 2008 at 11:18 PM, Larry Garfield <<a href="mailto:larry@garfieldtech.com" target="_blank">larry@garfieldtech.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Monday 19 May 2008, Darrel O'Pry wrote:<br>
</div><div>> I just think it wold be cool to support both options, as some items may be<br>
> user specific. I'm not excluding normal cache_set/cache_get. I'm still<br>
> think in terms of a more general cacheable module_invoke_all and not<br>
> specifically hook_*_info.<br>
<br>
</div>There may be an advantage to that, but that's separate from what I'm<br>
proposing. :-)<br>
<br>
It sounds like most people are in favor of something like this, though. Is<br>
anyone opposed to some written standards that we can then apply to code?</blockquote><div><br>It still remains to be seen if it's worthwhile.... Iterating over a few functions returning static arrays to to be merged vs a db_query() to be benchmarked... I personally think the db query will probably lose this race.<br>
</div></div>