assignment to pool and uie persist to member

Well hopefully it's for both. In the first instance we need 5 siloed (sp?) versions of a VOD service, fronted by a single 3900, as the builds come from our developers to functional testing on a private internal network. Then we have a load testing environment, with 2 versions fronted by a pair of 8900's, which is likely to be partially web exposed, and then finally a production environment, with 2 versions again with8900s, which will need some mechanism to ensure a newly deployed environment is operational before we flip a default pool to make it live for a gazillion users. I'd like to keep as much code as common as humanly possible, but without risking anything in the production environment. There is a security principle if all global users could add a paramter onto the query string, but I'd probably deem that to be trivial compared to all sorts of other risks that are much juicier. That said, I'm sure some public IP range block could be used.