Courageous
Wanderer
Ah, no, not at all. Actually, the whitelist would be a very cheap calculation, and if you knew what to put in it, by item-id, I'd gladly code it. Keep in mind that the cacheing algorithm for the tiles, in the default 1/96th size resolution, produces an enormous datastructure that would be far in excess of the size of any tile whitelist.
How about this: for the next release, I'll set up a runtime xml config file that establishes the white list. You can then play around with whitelisting tiles.
Any other problems? My main subliminal worry is that there might be situations in the code proper--some specific thing--where I might not have hooked code in the right places. As in with your example of being able to see GMs...
When you get more experience with it, I'd like to hear how well it performs. A very good basis in thought says the cach'er ought to make it a screamer under load. But still... that's a theory.
C//
How about this: for the next release, I'll set up a runtime xml config file that establishes the white list. You can then play around with whitelisting tiles.
Any other problems? My main subliminal worry is that there might be situations in the code proper--some specific thing--where I might not have hooked code in the right places. As in with your example of being able to see GMs...
When you get more experience with it, I'd like to hear how well it performs. A very good basis in thought says the cach'er ought to make it a screamer under load. But still... that's a theory.
C//