FreeThreadedDOMDocument <-> cache status
Hi
shortly, i'm implementing the FreeThreadedDOMDocument instead of DomDocument to increase speed.
But I have some practical questions about threads and cache.
- when an object is loaded as an Application()-value, remains it always in the cache until the cache is emptyed via an 'unload application' in iis or reloading the value in the Application() in asp page? Or is the cache size limited in such a way that new data push out oldest data?
- is the thread acting as an independed process on the machine, or only within the application itself (the website).
- is it possible to 'isolate' the threadprocess to give it a higher priority (in order to increase extra the speed for that process)?
Kabe
|