-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat: Autosharding protocol changes for req-resp protocols #1937
Comments
fryorcraken
added
E:1.2: Autosharding for autoscaling
See https://github.com/waku-org/pm/issues/65 for details
and removed
E:2023-1mil-users
labels
Sep 13, 2023
10 tasks
Suggested to drop this from |
fryorcraken
removed
the
E:1.2: Autosharding for autoscaling
See https://github.com/waku-org/pm/issues/65 for details
label
Oct 26, 2023
Iceboxing this as it's a cleanup/nice to have that does not have strong added value. May be done if it allows to simplify code/logic to enable work in the area. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This tracks work necessary to change req-resp protocol requirements for pubsub topic fields to be optional in wire specifications. This implies a spec change, changes to clients to use the simplified specs and changes to server-side Waku implementations to interpret client requests with no populated pubsub topics correctly.
Priority: Not critical for launch (all main benefits of autosharding is already achieved via API changes)
The text was updated successfully, but these errors were encountered: