8000 [Feat]: A suggestion to improve speed · Issue #6628 · coder/code-server · GitHub
[go: up one dir, main page]
Skip to content

[Feat]: A suggestion to improve speed #6628

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.

Sign up for GitHub

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

Jump to bottom
Closed
sky-sunnext opened this issue Jan 14, 2024 · 2 comments
Closed

[Feat]: A suggestion to improve speed #6628

sky-sunnext opened this issue Jan 14, 2024 · 2 comments
Labels
enhancement Some improvement that isn't a feature upstream:vscode Needs to be fixed upstream in VSCode

Comments

@sky-sunnext
Copy link

What is your suggestion?

VSCode can cause all connections to be blocked when uploading files, and this phenomenon is more pronounced when using low-speed FRP to penetrate VSCode into the public network. So why add an option to allow uploading files using other connections?

Why do you want this feature?

When using low-speed FRP, the VSCode section has a poor experience

Are there any workarounds to get this functionality today?

For example, allowing users to choose to open another HTTP/WS server for uploading? Or use P2P (WebRTC)+custom STUN server to achieve higher upload speed?
@sky-sunnext sky-sunnext added the enhancement Some improvement that isn't a feature label Jan 14, 2024
@code-asher
Copy link
Member

I think this should probably go in https://github.com/microsoft/vscode, I am not sure we would want to maintain a large architectural change like this in patch files here in code-server. 🤔

@code-asher
Copy link
Member
code-asher commented May 22, 2025 •
edited
Loading

Closing for now as an upstream issue. If someone implements this and VS Code turns it down, we could consider patching, if the diff is not too bad.

@code-asher code-asher closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2025
@code-asher code-asher added the upstream:vscode Needs to be fixed upstream in VSCode label May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Some improvement that isn't a feature upstream:vscode Needs to be fixed upstream in VSCode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@code-asher @sky-sunnext
0