Possible solution for FileBasedCachingProvider file locking issues.

I had an idea on the weekend.  In the FileBasedCaching provider the file locking comes about when two servers try to write the CacheFile at the same time.  This occurs because both servers have reloaded their own caches and need to create the dependency file.  Since both servers are trying to do exactly the same thing I thought that a Try Catch block around the code would allow the provider to work correctly.  The catch would jut have a comment that another server is trying to create the same file.

I haven't finished my web farm yet so i can't test this out.  Could someone else with a farm try this and let us know how it goes.?