TIME: mention server-time as an alternative #158
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
That's an interesting point about bouncers. If bouncers are expected to forward TIME to the upstream server, I guess we could recommend using the time tag on the RPL_TIME response instead? |
Yup.
Do existing servers supporting server-time attach a time tag to the RPL_TIME response? |
|
Done in #176 |
|
hmm, the underlying question isn't answered though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #154 (comment)
Though I am not sure this is correct in the presence of a bouncer. Bouncers would reply to
PINGwith their own time, whileTIMEwould be forwarded to the server, right?