[jbehave-dev] [jira] (JBEHAVE-889) Cache reload asynchronous, Pull request

[Christian Haas (JIRA)]

Christian Haas commented on JBEHAVE-889 Cache reload asynchronous, Pull request Additional info: For each reload request, a new, empty cache is created. As far as I could gather it, the cache has some sort of delta mechanism which would avoid reloading of unchanged data; This delta check is thus now useless, but might help for future extensions where the current cache is cloned to serve as basis for a new reload. Field experience will show whether this becomes necessary. Also, from the description of issue #1 about a slow editor with large files I'm not sure whether this fix applies here; It could be that iterating through the step candidates themselves for highlighting might be a second slow-down. But first things first, let's see if this change has any positive effect here. I based my changes on the recent merge from upstream yesterday, it should apply seamless. (Hoping my newly acquired git skills did the trick )

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email