-
Notifications
You must be signed in to change notification settings - Fork 273
lds: Add listener_filter_chain. #400
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
Changes from 4 commits
02b4a5e
74a163a
113052e
071ddd9
6f24f4d
0dd802c
2ce8e72
138d110
94773bf
fd02c81
5f41ccc
11d9ab4
362031f
a7e6fdf
d6f8842
e2a201a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -103,6 +103,13 @@ message Listener { | |
|
|
||
| // The type of draining to perform at a listener-wide level. | ||
| DrainType drain_type = 8; | ||
|
|
||
| // A list of individual listener filters that make up the filter chain for sockets accepted with | ||
| // the listener. These filters are run before any in the 'filter_chains', and these filters have | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Optional: you could refer to the |
||
| // the opportunity to manipulate and augment the connection metadata that is used in connection | ||
| // filter chain matching. Order matters as the filters are processed sequentially right after a | ||
| // socket has been accepted by the listener, and before a connection is created. | ||
| repeated Filter listener_filters = 9; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since this is a completely different type of filter from network filters, should it use a different type to describe it? Right now they have the same set of data, but possibly in the future they could be different. Prior art: HttpFilter is a different type.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1. I would do a
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. Assuming we don't need the deprecated_v1 stuff, ListenerFilter message now only has the name and config members. |
||
| } | ||
|
|
||
| message Filter { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence is a bit hard to read. Obviously this is a list of filters. What I want to know when should use use them and what action they would perform? How are they different from other filters.
If I guess correctly, this is a list of filters attached to socket listener. They do something before the listener accepts a connection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your guess would be almost correct. The rest of the comment states that these filters are run right after the listener accepts a connection (in the sence of the accept() system call).
I've reworded to the comment to not state the obvious and come to the point in the first sentence. Please have a look.