Request Routing
One of the many powerful features that a virtual directory or ldap proxy system can provide you with is the ability to route traffic to particular destinations based on various parameters, such as particular pieces of information within a search request, or the origin IP address or network that a request is made from.
Symlabs LDAP Proxy and Virtual Directory server come with a variety of plugins specific to routing LDAP traffic to particular destination servers depending on information within any LDAP request. So, for instance, you can route requests to servers dedicated to handling particular operations based on the type of operation being performed. This is very handy if you have a master-slave configuration within your LDAP infrastructure, as read operations can be routed to slave systems, while write operations can be routed to a master. There are a number of other interesting LDAP specific routing options available that are well worth exploring.
Virtual Directory Server is capable of working with a variety of protocols. The Route On IP plugin can be used to intercept traffic for any protocol at all, and redirect it to a particular server based on the original IP address or subnet that the request originates from, allowing you to present different information to different clients depending on where they are located.
Virtual Directory Server also includes some HTTP specific routing plugins that allow you to redirect traffic depending on particular things within the GET or POST request, such as the file extension being requested, or the host header. This allows you to do things like store media on an alternate host while presenting your pages as if the content is all stored together on one system.