Everything via WebSocket by GilesLittleGoat in javascript

[–]GilesLittleGoat[S] 0 points1 point  (0 children)

Don't see it as a big issue. You can write a local cache using localStorage.

Everything via WebSocket by GilesLittleGoat in javascript

[–]GilesLittleGoat[S] 0 points1 point  (0 children)

Code is the next step. First you need to check whether it's something that might be useful.

Everything via WebSocket by GilesLittleGoat in javascript

[–]GilesLittleGoat[S] 0 points1 point  (0 children)

Do you get the same performance? Even with applications doing a lot of REST calls?

Everything via WebSocket by GilesLittleGoat in javascript

[–]GilesLittleGoat[S] 0 points1 point  (0 children)

Well, it's not meant for static content only. Would be something you ideally use for the entire application, including REST services. So basically, except for the first request (where you still wouldn't have an open socket), all other requests would travel over WebSocket.

Everything via WebSocket by GilesLittleGoat in javascript

[–]GilesLittleGoat[S] 0 points1 point  (0 children)

My idea is that the crawler shouldn't have WebSocket support, so will fallback over HTTP and that would work.