binder: SecurityPolicies.allOf() and anyOf() should efficiently interop with AsyncSecurityPolicy
- Vorherrschende Sprache
- Java
- Sterne
- 12.1k
- Forks
- 4k
- Ø Merge
- 2 T. 17 Std.
- Gemergte PRs (30 T.)
- 37
Beschreibung
### Is your feature request related to a problem?
As it stands, these composite security policies can be used with AsyncSecurityPolicy, but they end up blocking an additional thread on Future.get() [here](https://github.com/grpc/grpc-java/blob/782a44ad62f84d19291b0771b56b431e6e723752/binder/src/main/java/io/grpc/binder/AsyncSecurityPolicy.java#L45).
### Describe the solution you'd like
We could create new allOfAsync() and anyOfAsync() methods or try to update the existing methods to special case AsyncSecurityPolicy..
Beitragsleitfaden
Rechercherichtung
Start by reading binder/src/main/java/io/grpc/binder/AsyncSecurityPolicy.java at the Future.get() call linked in the issue, then inspect the existing SecurityPolicies.allOf() and anyOf() APIs. Determine whether async-specific methods or special handling best avoids the extra blocking thread, and consider how the chosen API should preserve existing composite-policy behavior.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- security
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100