ctrl + return for submit has stopped working again
-
See the title. Seems to have happened at some point today
-
@Jaloopa what? again?
I assume the old "refresh the page" trick didn't bring it back?
EDIT: seems to be working for me on Chrome 51.numbers
-
@accalia hadn't tried refreshing, lets see what happens
Edit: OK, probably another websockets cockup
-
@Jaloopa said in ctrl + return for submit has stopped working again:
Edit: OK, probably another websockets cockup
eyup....
note to self.... websockets sexy but make damn sure if you use them to make your software A-OK when they're not usable too.
-
@Jaloopa said in ctrl + return for submit has stopped working again:
websockets
More like websuckets, amirite?
-
@accalia said in ctrl + return for submit has stopped working again:
note to self.... websockets sexy but make damn sure if you use them to make your software A-OK when they're not usable too.
Wouldn't it just be easier to make your software work A-OK without web sockets-- and then not use websockets?
Because they seem to have zero benefit.
Contrast with Javascript, for example. A simple form.
- Fallback version is plain HTML. Click Submit, it submits.
- Javascript version is still plain HTML, but when you click submit it shows a spinner
See, in that case the Javascript enhances the working functionality. What Websockets is doing is:
- Javascript version. Replaces the button with a different button. On click gathers all form data, packages it into a JSON payload, and POSTS it to the form's target
Wait, why do that? It isn't enhancing the process in any way. It's just doing what's already being done, except poorly.
-
@Lorne-Kates said in ctrl + return for submit has stopped working again:
Wait, why do that? It isn't enhancing the process in any way. It's just doing what's already being done, except poorly.
Sounds like Websockets aren't of much use on a forum, but what's the alternative for (say) a report that's going to take 45 seconds to run? Or something that might take several minutes?
-
@Lorne-Kates Websockets is really more for when you want a constant stream of communication back to the server, like an accurate progress bar on a long-running process, or a chat client. If it's stop and start like a forum, I'd be in favor of pure AJAX anyway.
-
@Yamikuronue But websockets keep the connection open between requests! That's more efficient somehow! Unlike HTTP/1.1 and HTTP/2, which only keep the connection open between re--I'll get back to you on that.
-
Can anyone tell me again why things like emoji, CSS and keybindings are delivered over the websocket connection?
-
Yeah, I got nothing.
-
@dkf said in ctrl + return for submit has stopped working again:
Can anyone tell me again why things like emoji, CSS and keybindings are delivered over the websocket connection?
because shiney-shiney is good, yah?
<With apologies to @Yamikuronue>
-
-
@Lorne-Kates said in ctrl + return for submit has stopped working again:
Because they seem to have zero benefit.
It's generally for when you want the server to initiate the communication, or at least that's how I understand it. So when, for example, another user mentions you, the server doesn't have to queue the notification until the next request comes, it can just write to the socket during the processing of another user's post.
Pretty much the only way to achieve similar behavior without websockets is long polling (and a few things that didn't really take off), and long polling is kind of a hack - there's a lot of wasted requests, and AFAIK there are some server-side considerations (separate requests are generally isolated or something), but I've never really looked into it..
-
@Yamikuronue said in ctrl + return for submit has stopped working again:
@accalia yah yah, shiny.
Filed under: Inside joke
-
@Yamikuronue said in ctrl + return for submit has stopped working again:
@accalia yah yah, shiny.
Filed under: Inside joke
Pickle Pee and Pumparum?
-
@Yamikuronue said in ctrl + return for submit has stopped working again:
@accalia yah yah, shiny.
Filed under: Inside joke
Your insides are shiny?
-
@Lorne-Kates said in ctrl + return for submit has stopped working again:
@Yamikuronue said in ctrl + return for submit has stopped working again:
@accalia yah yah, shiny.
Filed under: Inside joke
Your insides are shiny?
Better than OUTSIDES that are shiny, amirite?!
Filed under: fscking Twilight... Ruined forever
-
@ben_lubar said in ctrl + return for submit has stopped working again:
But websockets keep the connection open between requests!
I thought the actual thing here is that websockets aren't subject to the "30 seconds or so of CPU time and your thread is terminated" thing.
-
@Yamikuronue said in ctrl + return for submit has stopped working again:
shiny.
-
@FrostCat STUPID JELLYPOTATO
-
@FrostCat said in ctrl + return for submit has stopped working again:
@FrostCat STUPID JELLYPOTATO
Yeah, that image took WAY too long to load...