Community
Participate
Working Groups
Just to document an idea that came up in a discussion between Andre and me: Additional to the prefetching which pushes objects from the server to the client in advance, we could also think of providing an interface and implementation for prefetching strategies from the store to the server cache. E.g., currently, if the server is started, the cache is rather empty and not populated until the first client asks about an object. We could provide a configuration option so that the server cache is already filled on server start with, e.g., the resource tree or the content of one or more (user-configurable) resources. This way, the first client startup could happen faster and the server cache is always filled.
+1!
Rebasing all outstanding enhancements requests to version 4.0
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
This is already easily possible by listening to ILifecycleEvents of the repository.