Remove code path that passes a file handle to the renderer...

Remove code path that passes a file handle to the renderer
Since the code now does range request without any caching
the code path for passing file handle is not used any more.

Changes:
1. Remove response_data_file in webkit_glue::ResourceResponseHead
2. Remove response_data_file in net::ResourceInfo
3. Remove code that passes file handle using IPC
4. Remove code that passes file hadnle from network layer to ResourceDispatcherHost
5. Remove MediaResourceHandler
6. Remove code in disk_cache that expose the file handle
7. Remove ChromeURLRequestContext::CreateOffTheRecordForMedia() so no more OTR request context for media, in OTR mode simply memory cache is used
8. Reset cache size for media cache to default

BUG=12249
BUG=12256
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=17227

[scherkus (not reviewing), 2009-05-28 01:27:51]

Haven't looked at any of the code yet, but I believe the preferred bug format
is:
BUG=http://crbug.com/1234

[Alpha Left Google, 2009-05-28 05:35:12]

On 2009/05/28 01:27:51, scherkus wrote:
> Haven't looked at any of the code yet, but I believe the preferred bug format
> is:
> BUG=http://crbug.com/1234

I guess you either do BUG=1234 or http://crbug.com it will get updated?

[Alpha Left Google, 2009-05-28 18:33:35]

removed the code path that passes the file handle to the  renderer, so the
changes are:
1. No more file handle entry in the IPC message
2. No more media request contest (If we do sparse caching, we don't need this
and everything should under regular request context)
3. No more file handle entry in HttpResponseInfo
4. Removed the code that gets the file handle from the cache (There should be
any more code that need this functionality)

[Alpha Left Google, 2009-05-28 22:14:43]

Remove most of the code path but preserved the request context for media so
there will be a separate cache instance for media resources.

[rvargas (doing something else), 2009-05-29 02:50:43]

LGTM.