Right now the expression caches have no maximum size or expire time. The
FlexibleStringExpander cache shouldn't be a problem with those settings
because the expressions are like constants - they don't change during
program execution. The maximum size on the demo server runs around
3000-5000 entries, so I think we're safe there.
I'm concerned about the FlexibleMapAccessor cache though. Since IDs are
used to create expressions, there is a potential for that cache to grow
to tens of thousands. I think some kind of limit should be put on that
cache, but I'm not sure what they should be.
Any advice would be appreciated.
-Adrian
