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 ...
Hi Shadid, LoundesM
That is exactly what my client needs.
Their need isn't based on wanting to limit the traffic.
We indeed want to be able to route depening on values in the incoming request. The example LoundesM provided is not very far from our case.
We use customernumbers, ipadresses, macadresses which are translated to a technical ID via groovy script.
The technical ID is then used to return a specific template. Based on the value of this technical ID we can determine if our customer is "real" or "virtual" (for example: if technicalID > 1 000 000 return real else return virtual)
Preferably we would control this via groovy script as this would allow us the most precise control.
There are a few reasons for our need:
- Multiple APIs controlled by both internal and external parties on sometimes unstable environments
- Multiple independent testers at various different test levels
- Test automation of the GUI application using our VirtServer
- Developers of either the GUI application or the service layer (composite API) want it configured depending on their current development phase.
So at any given time different teams want the same GUI application or composite API configured to different endpoints which isn't feasible.
This option would help with the acceptance of our VirtServer setup tremendously.