[erlang-questions] Erlang-Java interface through ordinary ports

[Alex Arnon]

I had built a library to do just this, including monitoring/linking in case
either side dies etc.
jinterface takes a little bit of work to get around, but it's certainly
possible... my takeaway from this is that it's probably simpler overall to
use a node, since you'll probably get into managing serialization, queueing
and dispatch by yourself. The difference in effort is marginal either way.


On Tue, Jul 12, 2011 at 1:14 AM, Daniel Dormont <dan@REDACTED>wrote:

> Hello Erlangers,
>
> I would like to have an Erlang application (specifically the auth_external
> module in Ejabberd) communicate with a Java program I am writing. Not as a
> node, but rather using the port driver API, since that is what Ejabberd
> already supports. From the information I've seen, it shouldn't be too
> terribly hard - just listen for data in System.in, look for a two-byte chunk
> that when read as a short specifies the number of additional bytes to read,
> and repeat. I'm just wondering if this is something that's considered normal
> and reasonable to do, any gotchas I should be aware of, etc.
>
> The only reason I'm picking Java is the rest of my application is Java and
> I'd like to reuse some libraries and such.
>
> thanks,
> Dan
>
> _______________________________________________
> 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/20110712/641d5be0/attachment.htm>