Replies: 1 comment 2 replies
-
Discord itself supports sending and receiving data over the Websocket via JSON or ETF due their realtime websocket API being built on Erlang. The ETF encoding is actually also used by the Discord client itself when communicating over Websocket, and in general is a faster more compressed representation of the data when compared to JSON. As such, we implemented the encoding so that developers can choose for themselves which to use when dealing with Discord. This setting is accessible via JDABuilder#setGatewayEncoding(GatewayEncoding) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was pleasantly surprised to see the implementation of a decoder and encoder for the ETF whilst browsing the Javadoc. So as in the title, what's the motivation behind it?
Beta Was this translation helpful? Give feedback.
All reactions