Quote -
I think I see an inherent problem. Shouldn't the temporary cache size should be controlled from the program you're running rather than one that you are not? 

What program are you referring to? The IE component running inside Poser is still the IE component, and all IE settings apply. This is Microsoft's intentional design - that all apps that use web technology, regardless of where the data comes from or whatever, is going through the same service and configured in one place. Similar to using a printer driver - the printer driver settings are the same regardless of which application is doing the printing.

The IE browser is like a printer component, except it doesn't print, it display HTML/Javascript content on your screen in a standardized way.

I forgot that this thread raised the issue of thousands of cached XML files. I'm surprised they're cached at all. They are not documents that are to be retrieved over and over again. Something is misconfigured in this case. On all my systems, dynamic content delivered to a Flash application is never cached. By definition, these files are useless, since the application wants new information from the server on each request.

Quote - BTW. I never thought of this before. Would it be a problem if someone accidently ran a loop-back test during a Poser render? 

No.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)