Asynchronous UIs - the future of web user interfaces

Re:Asynchronous UIs - the future of web user interfaces by barefoot on Wednesday November 16, 2011 @02:47PM (#3244730)

I think there's a better solution for e-mail. The moment it reaches the server the UI unblocks.

Later, if there is an issue with sending your e-mail it alerts you inside your browser. If you're unreachable through your web browser it sends you a text. What's wrong with that?

[ Parent | on HN ]

Re:Asynchronous UIs - the future of web user interfaces by MatthewPhillips on Wednesday November 16, 2011 @03:01PM (#3244807)

So what you are saying is that the server, upon receiving the email request, immediately sends a 200 OK response and sends the email request to another server (or spawns a new thread). Isn't this probably what happens anyways? In the case of Gmail it's likely a comet request that is held until the email is finished sending. Is the former method really that much better?

[ Parent | on HN ]