remove parsed address cache

[plally]

The performance benefit from this is pretty small and complicating the caching logic to resolve #39 makes that difference even smaller, and in some cases worse.

It would be better to do caching around the CFCHTTP.GetOptionsForURL function

[Grocel]

The issue with complex caching logic as seen in #41 comes from removing invalid entries in every add/set call using a relatively expensive invalidation check for each cell. That's why I actually just table.Empty() the cache content on overflow without any other checks for my case shown in #39.

On set/add: It is a O(n) vs. about O(1) with a single cheaper O(n) on overflow which happen rarely in practice.

But because those string operations behind it are indeed not that expensive, removing the cache is fine too, I guess. For my case I use the limited cache in front of a way more expensive (e.g. networking) tasks.

[plally]

Would that actually be O(n). It should only have to loop over the expired items since they are ordered by time added in a queue.

[Grocel]

I'm not sure if we understand each other at the moment.

[plally]

I was talking about the complexity of setting an item on the cache structure I had in the other PR