The routing option is too limited to be useable today. At my current client we need the option to route certrain ranges to the real back end services, or the option to do so via scripting (return ...
My interpretation of Jeroen's original request would be something like this (speak up if its wrong :smileywink:)
with routing enabled at present a request is either served by the virt or the routed service based upon the operation (get, put etc)
for any given operation what if we want to limit some traffic to use the virt and some to use the actual service
i.e. we have some external people doing some testing and we're providing a virt for them to use, however some of our internal team are also using the virt and we want to expose them to some of the actual service functionality as becomes available to test before letting the external party also use that
if there was an input field with a year value for example, we could say to the external party enter the year value in the range 2011 - 2013, in this case they would all be served the virt response as per the standard dispatch rules as if routing was disabled
for the same request our internal testers used a range of 2014 - 2017, in this case the routing would kick in and they would be served the actual response from the service as opposed to the virt response
regards
Mike