Hi Juan
My wish to fix urlcache comes from the fact that World of Warcraft use it. The most common error seen in a wow logfile is: CommitUrlCacheEntry: entry already in cache - don't know what to do So I started looking at how to fix that. I assume that most people that play WoW installs a native wininet to solve this problem. But I like to run a full native wine to see these kind of problems. :)
I saw several bug reports in bugzilla, reporting problems with a full urlcache, which I also see sometimes in WoW. So I added that to the list of things I would like to do.
So I have been working on commit and internal cleanup. For now I am waiting for Piotr to commit his changes, as he got there first. After that I will rework my patches with things that Piotr haven't already done.
While working on the my changes, I have thought about doing further implementation and code rework. But now I will wait and see, how it looks after Piotr's changes.
On removing urlcache: A number of programs (seem to) use it, even though wine itself doesn't use urlcache that much. So removing urlcache would probably break a lot of running programs.
As to make wine use urlcache more, that would be something further down the line. I wont commit to doing that, but I have thought on how to work further on persistent cookies, which also uses urlcache.
Best Regards Morten Rønne
Den 05-04-2012 19:30, Juan Lang skrev:
Hi Morten and Piotr, I notice both of you are working on wininet's url cache. That's great: it's largely bitrot, and has been for years. My question is, what are you planning to fix? It seems like you're both running into some of the same issues right now, and it would be nice if you could coordinate a little. Ok, I lie: it'd be nice to get code from both of you ;)
If I were to guess, it looks like you're both working on eliminating corruption and deadlocks, both of which can occur right now. Fantastic.
Another thing that'd be nice to see is reducing the amount of disk space used. Morten, some of the patches you sent me do some of that, by removing files once they're no longer in use. (The patches I have do that too.) Piotr, were you planning to address this too?
A question that I have to ask is, would be better to eliminate the url cache altogether? Right now its only utility is to pass test cases, and conveniently fill up your disk. No requests are ever fulfilled from the cache. Either of you have any plans to tackle that?
Thanks, --Juan