Edgewall Software

Changes between Initial Version and Version 3 of Ticket #9938


Ignore:
Timestamp:
Dec 19, 2010, 9:57:15 PM (9 years ago)
Author:
Remy Blank
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9938 – Description

    initial v3  
    1010Since this requires the whole bunch of the default request dispatcher component, along with multiple other instances of components being either instantiated or referenced, overall servicing latency is rather high, especially for resources that lead to a 404 or 304 response.
    1111
    12 My proposition is now to introduce a StaticResourceCache component at the web.main level, which will then be used by both the chrome component for registering resources and the main _dispatch_request routine.
     12My proposition is now to introduce a `StaticResourceCache` component at the web.main level, which will then be used by both the chrome component for registering resources and the main _dispatch_request routine.
    1313
    1414The cache will be filled lazily, so for each resource currently not in the cache, the default request dispatcher will call chrome to process the request normally.