[erlang-questions] Two beautiful programs - or web programming made easy

[Joe Armstrong]

As I see it the web is predominantly built with one concurrency pattern.

A client (web browser) can do an RPC to a server

We can't (easily)

do an RPC from the server to the client
send an asynchronous message from server to client
send an asynchronous message from the client to the server

Of these four concurrency patterns three are crippled.

Instant messageing, for example,is trivial if you can push messages to a
client.

Turning web sockets off for security reasons is stupid.

The solution is to sandbox the thing that receives the messages
or if unsandboxed strongly authenticate the messages.

/Joe



and

On Sat, Feb 12, 2011 at 1:49 PM, Masklinn <masklinn@REDACTED> wrote:

> On 2011-02-12, at 13:15 , Ulf Wiger wrote:
> > Well, I read those links not as an indictment of websockets per se
> Why would you? They're not, they're just warnings that websockets are
> getting disabled in browsers due to being currently broken, and that this
> kind of approach is therefore nice as a research toy but can not be
> considered for serious work at this point.
>
> I don't believe I wrote anything against Joe's idea, I just forwarded short
> and mid-term issues with actually applying them outside of well-controlled
> demonstration environments.