The Wayback Machine - https://web.archive.org/web/20210111221226/https://github.com/gorhill/httpswitchboard/issues/301
Skip to content
This repository has been archived by the owner. It is now read-only.

Finer-grained ubiquitous rules #301

Closed
gorhill opened this issue May 25, 2014 · 4 comments
Closed

Finer-grained ubiquitous rules #301

gorhill opened this issue May 25, 2014 · 4 comments

Comments

@gorhill
Copy link
Owner

@gorhill gorhill commented May 25, 2014

Many users have asked about "scope inheritance". Scope inheritance is not something I will undertake because I don't know how this would ever work when considering all the complications.

However given the specific examples given, what would take care of the issues is really finer-grained ubiquitous rules. This potentially will affect negatively matrix filtering performance. Need to investigate faisability though, as this would take care of many of the issues raised.

@gorhill
Copy link
Owner Author

@gorhill gorhill commented May 25, 2014

Reference: #297, #227, #105.

@ohrly
Copy link

@ohrly ohrly commented May 25, 2014

Thanks and thumbs up!

@gorhill
Copy link
Owner Author

@gorhill gorhill commented May 28, 2014

Well this adds a good chunk of overhead. For each single cell, the following pseudo code needs to run in addition to the existing code:

if not locally graylisted
    if globally whitelisted
        return 'gdt'
    if globally blacklisted
        return 'rdt'

And a lot of cell may be visited when going up the matrix inheritance path, all the way up to the all cell.

And this not counting the complication of graylisting cells, like for example user graylist a cell in local scope in order to cancel specific rule in global scope, than later remove said rule from global scope leaving the graylisted cell uselessly explicitly graylisted.

Sigh...

gorhill added a commit that referenced this issue May 28, 2014
gorhill added a commit that referenced this issue May 28, 2014
@gorhill gorhill removed the important label May 28, 2014
@gorhill
Copy link
Owner Author

@gorhill gorhill commented May 28, 2014

Closing as "won't fix". Sorry, the required changes are scary. On the surface all is simple and easy. Digging under the surface, it's horrible. So we will have to accept the extension can't and won't do everything that comes to mind.

So back again to the same point: scopes are sandboxes, and I can't argue about this anymore. My only suggested alternative from this point forward is to fork the code, I can't implement this without compromising the sanity of the code (and mine I suppose).

@gorhill gorhill closed this May 28, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.