Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MXMLMatchers should cache internal matcher instances #26

Open
drewbourne opened this issue Apr 21, 2010 · 0 comments
Open

MXMLMatchers should cache internal matcher instances #26

drewbourne opened this issue Apr 21, 2010 · 0 comments

Comments

@drewbourne
Copy link
Owner

MXMLMatchers currently create a new instance of their internal matcher each time createMatcher() is called. In a performance sensitive scenario like rules engines this becomes prohibitively expensive in time, and memory. Cache the internal matcher until invalidated by property changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant