[ic] usefulness of mv_pc

[interchange-users@icdevgroup.org (Jeff Dafoe)]

    mv_pc appears to start back at 1 for each new session.  In order to
truly prevent caching, shouldn't it be a random number?  If aol or some
equally-aggressive cache is caching
www.mystore.com/mystore/0023.html?mv_pc=3 what would prevent this from being
served from the cache to any sessions coming through that same caching
server that happen to be requesting the same mv_pc value (which is most
likely to occur within the first few clicks from the landing page)?
    Would there be any repercussions if I were to modify the code to
generate a random number?

Jeff