[erlang-questions] web sockets almost working ....
Thu Dec 10 17:17:08 CET 2009
Perfect. Inherent nature of the Erlang (message passing and its
concurrency handling) is perfect fit for Websocket. Json would have
been easy without resorting to json modules if it is available as BIF
in erlang as you suggested earlier somewhere, nontheless it is not big
deal to provide json capability and we will certainly do it.
On Thu, Dec 10, 2009 at 10:08 AM, Joe Armstrong <erlang@REDACTED> wrote:
> Brilliant - the race is on - then add a json/erlang term format
> abstartionn layer on top
> of the raw socket interface.
> Another group should do an in-line chat engine
> Use a DHT for the users and we could make an infinitly scabale IRC engine :-)
> On Thu, Dec 10, 2009 at 5:01 PM, Senthilkumar Peelikkampatti
> <senthilkumar.peelikkampatti@REDACTED> wrote:
>> Thanks for heads up. We are working on websocket and repository
>> is setup at http://github.com/sendtopms/erlwebsockserver. Initial
>> target is Mochiweb and we are planning for supporting other app
>> servers like inet and yaws.
>> On Thu, Dec 10, 2009 at 9:55 AM, Max Lapshin <max.lapshin@REDACTED> wrote:
>>> On Thu, Dec 10, 2009 at 6:51 PM, Dmitry Belyaev <rumata-estor@REDACTED> wrote:
>>>> If this feature worked through HTTP then server side would have to
>>>> extract message from HTTP packet. In example shown there was no games
>>>> with HTTP.
>>>> What about proxy servers, I hope they will be redesigned to let WS work.
>>> Look, from server point of view, there is no difference between comet
>>> and web socket.
>>> Differs only the common time of being connected.
>>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>>> erlang-questions (at) erlang.org
>> Senthilkumar Peelikkampatti,
>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>> erlang-questions (at) erlang.org
More information about the erlang-questions