You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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. 🤔
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?
The text was updated successfully, but these errors were encountered: