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

Gateway Guild Sharding #31

Merged
merged 2 commits into from
May 13, 2016
Merged

Gateway Guild Sharding #31

merged 2 commits into from
May 13, 2016

Conversation

b1naryth1ef
Copy link
Contributor

This PR adds documentation around gateway guild sharding planned within #17.

@b1naryth1ef b1naryth1ef self-assigned this Apr 25, 2016
@@ -89,6 +89,7 @@ Used to trigger the initial handshake with the gateway.
| properties | object | connection properties |
| compress | boolean | whether this connection supports compression of the initial ready packet |
| large_threshold | integer | value between 50 and 250, total number of members where the gateway will stop sending offline members in the guild member list |
| shard | array of two integers (shard_id, num_shards) | used for [Guild Sharding](#DOCS_GATEWAY/sharding) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the shard key a tuple when using ETF? Maybe this should be clarified here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'll accept a tuple or list.

@jhgg jhgg mentioned this pull request Apr 26, 2016
4 tasks
@jhgg jhgg merged commit bf4c11d into master May 13, 2016
@night night deleted the feature/gateway-guild-sharding branch June 6, 2016 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants