-
Notifications
You must be signed in to change notification settings - Fork 431
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
Add Top Level Client and Server Objects #236
Conversation
290d87f
to
8ff3ef5
Compare
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 looks good.
A few points, though:
- I think this PR should add
client
andserver
to the list of placesgeo
is expected to be nested. - I think this PR should add
client
andserver
to the list of placesuser
is expected to be nested. - I also think it would be helpful if the definitions the the connection endpoints mentioned their expected pair explicitly: client & server are meant to be used together, and source & destination are meant to be used together.
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.
If #179 is merged then I think we want to add the |
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.
LGTM
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.
Excellent. LGTM
Just like client and server (elastic#236).
d342200
to
a199c48
Compare
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.
LGTM
d4fa25b
to
da793f1
Compare
Just like client and server (#236).
This PR closes #63 by adding the
client.*
andserver.*
top level objects to contain fields used in connection/session level events.Many thanks to those who expended time, energy, and passion in issue #63 along the way!