4 ms·

Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.

by magila 7y ago

Andrex 7y ago
Good catch, and the migration page kinda glosses over that. They are asking for input and use cases, though. "Q: My app uses the chrome sockets API to do networking. Can this be done with the open web? You might be able to do what you need with WebSockets. However, to use this, you will likely need to change the remote end of your connection. If that isn't possible, we'd like to hear more about your use case—please let us know about what you're trying to accomplish via the Chromium issue tracker.[1]" 1. https://bit.ly/new-fugu-request https://bit.ly/new-fugu-request
- ronsor 7y ago
  This is bad. Simple TCP and UDP sockets are the foundation of the internet.
  - Andrex 7y ago
    Correct, but they are not the foundation of the Web -- HTTP is, and web specification writers are only concerned with creating APIs for the web platform (hence why Web Sockets is an upgraded HTTP connection, not lower level like raw TCP or UDP.)
plopz 7y ago
What are the obvious reasons? Many game devs would absolutely love to have UDP available on the web in order to do proper networking.
- Andrex 7y ago
  Extremely good information and background context is available in this article: https://gafferongames.com/post/why_cant_i_send_udp_packets_from_a_browser/ https://gafferongames.com/post/why_cant_i_send_udp_packets_f... The big issue is trying to make UDP "safe" enough security-wise for the web platform, and such considerations are generally taken extremely seriously. If a vulnerability were discovered, the Google Chrome userbase could become a botnet capable of DDOS pummeling any website. Workarounds apparently exist for UDP over WebRTC, but it's a very "bulky" solution.
miohtama 7y ago
Does this mean no longer SSH terminals for Chromebooks?
pier25 7y ago
The last Chrome OS app I worked on for education used UDP to send broadcast packets in the classroom and find other devices to be able to communicate via WebSockets. I don't work there anymore but if one of the schools using that app bought Chromebooks without support for Android apps it's going to be a shit show in 2021.
deleted 7y ago
[deleted]

Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.

by magila 7y ago

Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.

Andrex 7y ago

Good catch, and the migration page kinda glosses over that. They are asking for input and use cases, though. "Q: My app uses the chrome sockets API to do networking. Can this be done with the open web? You might be able to do what you need with WebSockets. However, to use this, you will likely need to change the remote end of your connection. If that isn't possible, we'd like to hear more about your use case—please let us know about what you're trying to accomplish via the Chromium issue tracker.[1]" 1. https://bit.ly/new-fugu-request https://bit.ly/new-fugu-request

ronsor 7y ago
This is bad. Simple TCP and UDP sockets are the foundation of the internet.
- Andrex 7y ago
  Correct, but they are not the foundation of the Web -- HTTP is, and web specification writers are only concerned with creating APIs for the web platform (hence why Web Sockets is an upgraded HTTP connection, not lower level like raw TCP or UDP.)

plopz 7y ago

What are the obvious reasons? Many game devs would absolutely love to have UDP available on the web in order to do proper networking.

Andrex 7y ago
Extremely good information and background context is available in this article: https://gafferongames.com/post/why_cant_i_send_udp_packets_from_a_browser/ https://gafferongames.com/post/why_cant_i_send_udp_packets_f... The big issue is trying to make UDP "safe" enough security-wise for the web platform, and such considerations are generally taken extremely seriously. If a vulnerability were discovered, the Google Chrome userbase could become a botnet capable of DDOS pummeling any website. Workarounds apparently exist for UDP over WebRTC, but it's a very "bulky" solution.

miohtama 7y ago

Does this mean no longer SSH terminals for Chromebooks?

pier25 7y ago

The last Chrome OS app I worked on for education used UDP to send broadcast packets in the classroom and find other devices to be able to communicate via WebSockets. I don't work there anymore but if one of the schools using that app bought Chromebooks without support for Android apps it's going to be a shit show in 2021.

deleted 7y ago

[deleted]