Edgewall Software

Changes between Initial Version and Version 1 of Ticket #6826


Ignore:
Timestamp:
Feb 13, 2008, 9:14:29 PM (14 years ago)
Author:
Christian Boos
Comment:

The RepositoryManager pre_process_request does guard against the secondary requests (the if handler is not Chrome(self.env): test does that).

The timeline pre_process_request does nothing and its post_process_request does also a check (the if data: test).

So in both cases, there's no real performance impact.

But for the next release, I'd like to change the way the repository synchronization is done (as that's not scalable with the MultipleRepositorySupport) and that IRequestFilter filter will be history.

Setting milestone to 0.12 as a reminder to clean-up the IRequestFilter.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6826

    • Property Owner changed from Jonas Borgström to Christian Boos
    • Property Milestone 0.11.10.12
    • Property Component generalversion control
    • Property Severity normalminor
  • Ticket #6826 – Description

    initial v1  
    1 I tested work ReposytoryManager.sync
    2 Found that it is called each time during the RequestDispatcher.
    3 And when the request was "js", "css" or "png" file, these filters are still operable. Also called filter of TimelineModule.
     1I tested work !RepositoryManager.sync
     2Found that it is called each time during the !RequestDispatcher.
     3And when the request was "js", "css" or "png" file, these filters are still operable. Also called filter of !TimelineModule.
    44I believe that this is unnecessary, they should operate only for the modules.
    55