Erlang OTP wire protocol implemented in a Java library

[David Pollak]

http://www.theserverside.com/tt/articles/article.tss?l=IntegratingJavaandErlang

This might be a good transport layer for remote Actors.

[Eric Willigers]

David Pollak wrote:
> http://www.theserverside.com/tt/articles/article.tss?l=IntegratingJavaandErlang 

Note the conclusion. As Martin has put it, Scala would let him stop
sitting between two chairs.

[Paul LaCrosse]

David Pollak-2 wrote:

http://www.theserverside.com/tt/articles/article.tss?l=IntegratingJavaandErlang

This might be a good transport layer for remote Actors.

Maybe..., how about JGroups for the transport? (http://www.jgroups.org)

The transport stack is very configurable...

[Bill Venners]

Hi All,

For building distributed systems on the JVM, I'd also look at Jini. It  
has nice tools for discovering other nodes, dealing with partial  
failure, etc. It's now an Apache project. I'm not sure what the  
requirements or problems are currently with remote Actors, so I'm not  
sure if Jini would be a good fit, but it is certainly something I'd  
recommend looking at.

Bill


On Jan 10, 2008, at 10:33 AM, Paul J. LaCrosse wrote:

>
>
>
> David Pollak-2 wrote:
>>
>> http://www.theserverside.com/tt/articles/article.tss?l=IntegratingJavaandErlang
>>
>> This might be a good transport layer for remote Actors.
>>
>
> Maybe..., how about JGroups for the transport? (http://
> www.jgroups.org)
>
> The transport stack is very configurable...
> --
> View this message in context: http://www.nabble.com/Erlang-OTP-wire-protocol-implemented-in-a-Java-library-tp14717081p14736481.html
> Sent from the Scala - Lounge mailing list archive at Nabble.com.
>
>

[Alex Blewitt]

On Jan 10, 2008 5:34 PM, Bill Venners <bv-jackrabbit@...> wrote:
> Hi All,
>
> For building distributed systems on the JVM, I'd also look at Jini. It
> has nice tools for discovering other nodes, dealing with partial
> failure, etc. It's now an Apache project. I'm not sure what the
> requirements or problems are currently with remote Actors, so I'm not
> sure if Jini would be a good fit, but it is certainly something I'd
> recommend looking at.

I think the key point of using the Erlang format is not 'my format's
better than yours' but because it offers one thing that the others do
not: seamless interoperation with Erlang.

Alex.

[Paul LaCrosse]

... or even this:

http://jgcs.sourceforge.net/_Media/doa-06-13.pdf

This project is attempting to standardize a group communications API, and (supposedly) already works with JGroups, Appia, and Spread.

Remote actors could even be set up to work as RAIA (redundant array of inexpensive actors), along the lines of RAID and RAIDs (see http://sequoia.continuent.org/HomePage - built using jGCS), where any actor of a suitable type could be chosen from one of many available nodes.

[John D. Heintz-3]

Interoperation with Erlang is a nice property.

Perhaps JGroups or Jini could be used for service discovery but not
for the message transport?

Erlang has some library support to enable group discovery here in a
"process groups" module  http://erlang.org/doc/man/pg.html, but the
message transport still uses the standard Erlang protocol.

John

On Jan 10, 2008 11:59 AM, Alex Blewitt <alex.blewitt@...> wrote:

> On Jan 10, 2008 5:34 PM, Bill Venners <bv-jackrabbit@...> wrote:
> > Hi All,
> >
> > For building distributed systems on the JVM, I'd also look at Jini. It
> > has nice tools for discovering other nodes, dealing with partial
> > failure, etc. It's now an Apache project. I'm not sure what the
> > requirements or problems are currently with remote Actors, so I'm not
> > sure if Jini would be a good fit, but it is certainly something I'd
> > recommend looking at.
>
> I think the key point of using the Erlang format is not 'my format's
> better than yours' but because it offers one thing that the others do
> not: seamless interoperation with Erlang.
>
> Alex.
>

--
John D. Heintz
Principal Consultant
New Aspects of Software
http://newaspects.com
http://johnheintz.blogspot.com
Austin, TX
[phone]