When you do an IISReset the IIS cache will be cleared and then will start to be rebuilt after it starts back up as client requests come in. If you update a file then the older cached file will become stale and IIS will serve the updated file and update the cache with the new file.
IISReset (although harsh) will clear the IIS cache but it won't do anything with local caches in proxies or clients. Maybe you've just got the terminology mixed up a bit, but there isn't any concept of "resent" when it comes to caching. It's all request based. If a client requests something and it's found in a cache then it'll get served from the cache. You'll need to force content expiration on your files if you will be maintaining the same filenames.
It is only necessary one parameter could be
"?version=1" for first change,
"?version=2" for second change, it is practical and single to know the next value. Also you can use a GUID if you want :
"?version=4747b320-62ce-11cf-a5d6-28db04c10777" or you can use the date and time
"?version=20130220175025" for 2013/02/20 17:50:25.