HTTP application servers routing strategies and scenarios
You can use the following scenarios to send packets to HTTP application servers:
| Strategy | Scenario | |
|---|---|---|
| Sequential strategy
RECOMMENDED | Scenario 1 | Sending the same packet with reliability to one out of
distinct destination URLs in a same application server. The
packet is sent to the first destination URL, and only sent to the next
if the previous one is not available.
-> The packet is only sent to the first destination URL that has answered successfully. |
| Scenario 2 | Sending simultaneously with reliability the same packet to
one distinct destination URL in separate application servers.
All application servers must be in the same AS routing profile.
Optionally, each application server can have several destination URLs
also using the sequential strategy.
-> All the destination URLs have received the same packet with no delay, optionally with redundancy. | |
| Blast strategy
WILL BE DEPRECATED | Scenario 3 | Sending the same packet to all destination URLs in a same application server, one after another. There is a short delay between transmissions. Only used for existing application servers, it must not be used for new application servers. |