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

web3.js Roadmap – February 2023 – Discussion thread #1143

Closed
steveluscher opened this issue Feb 2, 2023 · 6 comments
Closed

web3.js Roadmap – February 2023 – Discussion thread #1143

steveluscher opened this issue Feb 2, 2023 · 6 comments

Comments

@steveluscher
Copy link
Collaborator

What do you want to see accomplished in @solana/web3.js in the month of February 2023?

Milestone: https://github.com/solana-labs/solana-web3.js/milestone/1

@mPaella
Copy link

mPaella commented Feb 19, 2023

Wanted to get thoughts on implementing a MultiConnection/ConcurrentConnection class, which allows the dev to specify multiple RPC URLs.

We have an implementation of this, and found it essential for reliability. Considering compression as well, with many RPCs not supporting it (at least not yet), having this would be helpful

@steveluscher
Copy link
Collaborator Author

Wanted to get thoughts on implementing a MultiConnection/ConcurrentConnection class, which allows the dev to specify multiple RPC URLs.

You're probably really going to like what I'm cooking up for the web3.js rewrite. I'll try to remember to tag you when I have a PR ready that's relevant to this.

In the meantime, say more. How do you use multiple RPC URLs? Are the extra URLs fallbacks for a primary one? Do you round-robin them? Are some dedicated for use with certain methods? Tell me all the use cases, @mPaella.

@mPaella
Copy link

mPaella commented Feb 21, 2023

Awesome, excited to see it. Is there a central place tracking the rewrite?

The main use case for us is just protection from upstream outages; This used to be a much larger problem when RPCs/Solana were less mature, but has gotten a lot better over time. Using a simple Promise.any() has been sufficient in most cases, and we use it for pretty much every method.

@steveluscher
Copy link
Collaborator Author

Is there a central place tracking the rewrite?

For background on the principles off which the rewrite will hang, take a look at #1111. For everything else just watch the packages/library directory, and all of the micropackages springing up around it.

@steveluscher
Copy link
Collaborator Author

Alright, that's a wrap on February. Let's take it to March! #1186

@github-actions
Copy link
Contributor

Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants