Persistence to a server for Web and Flash content

Aaron is right, it's more complicated that it would appear at first blush. Silo persistence for applets running on the same server/same IP, varying on port, is commonly implemented. Varying on IP but still requiring persistence to the same physical server is an uncommon requirement, I'd guess because it is difficult to implement and easy to work around in most cases.

 

 

I'd double check the requirement that both services must run on port 80. Understandable if you want the clients to connect on port 80 for both hostnames, but that doesn't mean you can't have LTM perform port translation for one app so both can run on the same IP address, different ports, then apply persist across services. That's the most commonly implemented silo persistence scenario.

 

 

Failing that, perhaps there is something common to the server responses in each pool that could be used as a persistence token? A session ID of any description would fit the bill.

 

 

HTH

 

/d