Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

efficient use of taps (and their input streams) which have the same filter #181

Closed
ghost opened this issue Jan 18, 2022 · 1 comment · Fixed by #186
Closed

efficient use of taps (and their input streams) which have the same filter #181

ghost opened this issue Jan 18, 2022 · 1 comment · Fixed by #186
Labels
enhancement New feature or request

Comments

@ghost
Copy link

ghost commented Jan 18, 2022

No description provided.

@ghost ghost added the enhancement New feature or request label Jan 18, 2022
@ghost ghost self-assigned this Jan 18, 2022
@ghost
Copy link
Author

ghost commented Jan 20, 2022

different policies using same tap+config should use same instantiated tap so as to only parse stream item (i.e. packet) once

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants