[mapguide-internals] Tile service request queuing

[UV]

as the decision if to use the cache or not is way inside the thread 
running the tile service
it seems a rather complex quest to feed this into the threadpool to 
prioritize the requests queue for the  ACE Reactor
this would require something like 2 stage pipelined thread pools .... 
one pool to evaluate the request
another pool to process it.....

this is better left to different server nodes
if the bottleneck is the max connections a webcache front end could 
alleviate the situation
I reckon it would be smarter to cache the tiles in front of the MGOS 
server for high performance scenarios



Zac Spitzer wrote:
> It's my understanding that with the tile service, tile requests which
> require rendering will
> block tile requests which simply require serving an existing tile when
> max connections
> has been reached?
>
> Is that correct?
>
>