cookie persistence mixed with httpclass uri routing

Hi,

Can someone clarify what happens if I have a virtual server with a cookie persistence profile combined with a number of httpclass profiles?

If we have a number of web apps on different servers (and so different pool members) for different uris, and they each require persistence, won't this collapse in a heap if a user wants to use more than one service? The cookie will cover the entire domain still, so will need to have that cookie purged before they can use the next service? I can't see any way that selecting a different class would work at all.

Is this going to need to end up as a bespoke irule? i.e. a version of the last example here? https://devcentral.f5.com/wiki/iRules.persist.ashx and if so, should I ditch httpclass references altogether to avoid duplication?

Alternatively, what about a generic iRule to do a "persist insert" with a cookie value of "persist_[first level of HTTP::path]"? this would then be able to be applied and forgotten about, and applied to multiple virtual servers wihout the need to ditch httpclass profiles.