Mike Jackson wrote:
Richard Megginson wrote:
> Views and VLV (Virtual List Views) are different. Views allows you
> to impose a hierarchical DIT upon a flat tree (virtually). VLV is
> paged search results.
So, do you Rich have any tips how to disable VLV?
Although I still don't see the reason why somebody would want to do
this. Are there misbehaving clients on your network, or what?
Outlook uses VLV's, but if the VLV indexes it uses are not actually
created, you get really bad performance and some "wierd" errors in
outlook. Assuming outlook only uses this if the server says it supports
VLV controls, disabling this in theory would make outlook "work better"
than with vlv's supported by the server, but no vlv index created.
The other app that uses VLV's that I know of is the Directory server
java console. If you disable VLV's it can affect performance there as well.
What is the reason you want to disable VLV's? If it is because of
Outlook, it would actually be better overall to create the VLV indexes
that outlook uses - they are fairly easy to create, and outlook's use of
vlv indexes is pretty consistent.
FWIW, Outlook uses VLV indexes for it's ldap addressbook functionality,
but one other bit of tuning you need to do for Outlook is index the
displayname attribute (even if you have no entries in the server with a
displayname value, you need to index the attribute to prevent a
sequential search of entries to realize this).