[erlang-questions] integrating nodejs with erlang code

[Son Tran-Nguyen]

Hi list,

I just want to chime in my 2 cent. I have been thinking about the
communication between Erlang and other languages for a while, and of course
you can write port to do so but there are problems with them.

So I was thinking, why don't we just use a message queue system like
RabbitMQ to act as the broker in between languages. Most message queue
systems have driver for most languages. We just need to implement an RPC
over messages. And we have total control over them.

I'm probably not familiar enough with Erlang but I think it maybe a better
choice.


Sincerely,


Son Tran-Nguyen


On Wed, Apr 10, 2013 at 7:15 PM, ノートン ジョーセフ ウェイ ン <norton@REDACTED
> wrote:

>
> Aman -
>
> Hello.  I'm currently building a Scheme interpreter for the Erlang VM (
> https://github.com/the-concurrent-schemer).  I drafted a data model that
> maps Scheme to Erlang and then built a Scheme token scanner, a Scheme datum
> parser, and the basics for a Scheme interpreter.
>
> I don't know much about JS (or Scheme for that matter) but feel free to
> contact me directly if you have questions or find any of this relevant to
> your interest about implementing JS in Erlang.  Good luck!
>
> Cheers,
>
> Joe N
>
> On Apr 11, 2013, at 03:49 , aman mangal <mangalaman93@REDACTED> wrote:
>
> Hi,
>
> How can I go about implementing JS in erlang? This seems interesting to
> me. Please tell me what do you mean by implementing JS or node.js in erlang?
>
> Aman Mangal
> 3rd year Undergraduate
> Department of Computer Science & Engineering
> IIT Bombay
> www.cse.iitb.ac.in/~amanmangal
>
>
> On Wed, Apr 10, 2013 at 10:42 PM, Zheng Zhibin <witeman.g@REDACTED>wrote:
>
>> beam.js would be one way to build node.js into Erlang :)
>>
>> Cheers
>> Ben
>>
>> 在 2013-4-10，下午11:46，Robert Virding <robert.virding@REDACTED>
>> 写道：
>>
>> The most efficient way of connecting Erlang with node.js would be, of
>> course, to implement JS and hence node.js in Erlang. Maybe not the easiest
>> way, but definitely the most efficient connection. :-)
>>
>> Robert
>>
>> ------------------------------
>>
>> *From: *"Joe Armstrong" <erlang@REDACTED>
>> *To: *"Eduardo Gurgel" <edgurgel@REDACTED>
>> *Cc: *"Ali Attarwala" <ali.attar@REDACTED>, "Shailesh Tyagi" <
>> shailesh@REDACTED>, "wncc iitb" <wncc_iitb@REDACTED>,
>> "Erlang" <erlang-questions@REDACTED>, "chirag jain" <
>> chirag.jain@REDACTED>
>> *Sent: *Wednesday, 10 April, 2013 11:14:19 AM
>> *Subject: *Re: [erlang-questions] integrating nodejs with erlang code
>>
>>
>> Just curious, but what is the *least efficient* way of connecting node.js
>> to Erlang.
>>
>> If I were doing this I'd start with the least efficient method, build my
>> app, measure, then optimize if
>> necessary.
>>
>> If the optimization is not necessary you have saved yourself a whole lot
>> of work.
>>
>> Alternatively, write the code and if it is not fast enough wait ten years.
>>
>>
>> Cheers
>>
>> /Joe
>>
>>
>>
>>
>> On Tue, Apr 9, 2013 at 2:11 PM, Eduardo Gurgel <edgurgel@REDACTED>wrote:
>>
>>>
>>>
>>>
>>> On Mon, Apr 8, 2013 at 12:37 PM, aman mangal <mangalaman93@REDACTED>wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> What is the most efficient way to pass events/data from erlang
>>>> processes to nodejs and vice versa? Setting up a tcp socket may be slower
>>>> or inefficient. I was thinking of doing something native. Both erlang and
>>>> nodejs provide libraries(NIF) to call C functions but none of them provide
>>>> an efficient implementation for calling erlang/nodejs functions from C or
>>>> C++ as far as I know. Please suggest some ideas!
>>>>
>>>>
>>> You could take a look on BERT RPC:
>>>
>>> https://github.com/rtomayko/node-bertrpc
>>>
>>> https://github.com/mojombo/bert.erl
>>>
>>> Right now, bert-rpc.org is returning 404, but it was up two days ago:
>>>
>>> http://bert-rpc.org/
>>>
>>> Maybe checking cached webpage on bert-rpc.org may help you.
>>>
>>> --
>>>
>>> Eduardo
>>>
>>>
>>>
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>
>>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130410/1caae89f/attachment.htm>