Community help wikis per release

[Ross Peoples]

Brent Saner wrote:
> Oooohhh...you mean implement both. I wasn't thinking that direction.
> Yeah, in that case I think the way you were describing would work. However,
> it'd need to be optimized. If it got heavy traffic (I'm assuming it won't
> but it's better to be best prepared instead of worst implemented), that
> could start to suck up a non-negligent amount of memory, methinks.
> 

I'm sure there's a way to do it without causing too many memory
problems. Worst case, you could just make it cache the generated table
until the compatibility matrix is modified. But I don't think it would
be memory intensive enough to do that. Then again, I'm no master php
coder, so I could be totally wrong, but I've done some tinkering before
with something similar.