Re: [Exist-development] default perms in collection.xconf do not seem to work

[Chris T. <chr...@gm...>]

Wolfgang,

Thank you for that summary. It confirms my anecdotal experience that the system seemed to be converging and that the major developments were coming to a close. The improvements in indexing and performance have been quite noticeable for us and greatly appreciated.

I can work with the permissions issue I think - it just kind of caught me off guard. As you pointed out in another post there's a lot of stuff that does

Chris


On Oct 18, 2011, at 7:49 PM, Wolfgang Meier wrote:

>> In fact what what other major items are on the to do list for the next stabilization - 1.6?
> 
> There are not many issues which block a first beta release towards the
> next stable version:
> 
> * there's a deadlock situation in the security manager - or rather:
> the Configuration class which reads account information. This is easy
> to reproduce but not so easy to fix. The changes Adam mentioned should
> be addressing this issue.
> * we have to provide a faster method for backing up large databases.
> This was discussed on this list a few days ago.
> * a few changes on the surface: we started to move all demo code out
> of trunk and into installable packages. This has to be finished and
> the web site changed accordingly to explain people how to get to the
> demos.
> 
> Apart from this, I have one thing on my list to further improve
> performance. It is not required for 1.6, but would be nice to have:
> redesign the range index in the same way as the structural index. The
> reorganization of the structural index has led to a major performance
> boost for complex queries. Now it's the range index which is blocking
> further speed ups and should be changed along the same lines.
> 
> Wolfgang