Unfortunately I can't describe too much about the architecture other
than to say that the Erlang VMs will be running on embedded hardware
(still using Linux) and shall be monitoring traffic streams on those
devices as well as exchanging state information between them. The key
to the Erlang portion is "5 nines" reliability - that stuff can not
crash. The central Java application provides certain analytics and
application "smarts" to the whole system. There isn't a technical
reason why Java was chosen -- we just selected a language from the
available development pool (in fact there are stronger reasons for
doing that work in Erlang IMO).

Initially I'm just after an IPC, in which case jinterface should work
just fine (I've already got experience developing cnode interfaces, so
I know the pitfalls of that solution).

I can see a number of benefits of Erjang:

* Supervision of the Erjang VM (and by extension the JVM) from the
distributed Erlang VMs using the OTP supervision methods.

* No need to add call backs or other hooks in the interface as new
functionality is added.

* We need an Erlang VM on the same host as the JVM - using Erjang
would negate this need.

Mainly though, the ability to use features of both languages in a
"native" manner, has the greatest appeal.

I do however have enough stuff to get starting with.

Many thanks

Matt