[erlang-patches] [jinterface] transport factory implementation

[Dmitriy Kargapolov]

Two test cases show how to setup a custom transport in different ways,
may be considered as examples.

In general there are no prerequisites from other components.

One use case is implementing ssh-tunnel for Java client while connecting
to regular Erlang node. This is useful for making secure connection
between Java client and Erlang server node(s). Such a transport could
use, for example JSch for client, on the server side there will be
regular TCP connection established from sshd to beam (or to epmd
process, when client queries EPMD).

Other use may, of course, require some development on Erlang side as
well. This is not covered by this work.

On 01/06/2015 11:07 AM, Vlad Dumitrescu wrote:
> Hi!
>
> Thanks for this. I will look closer at the code in the next days. My
> first comment is that I think there should be more examples on how to
> set up a different transport and maybe on how to implement other
> transports. I suppose that a prerequisite for this to work is that the
> Erlang nodes and epmd support and use that transport method too?
>
> best regards,
> Vlad
>
>
> On Sun, Jan 4, 2015 at 7:02 PM, Dmitriy Kargapolov
> <dmitriy.kargapolov@REDACTED <mailto:dmitriy.kargapolov@REDACTED>>
> wrote:
>
>     Transport factory basic implementation added. This makes possible
>     creating connections between nodes using ssh channels or ssl.
>     Default transport factory based on standart Socket/ServerSocket
>     classes is provided. Modifications are backward compatible.
>     Custom transport factory may be specified using 2 ways - via
>     system property or defining special tuner class.
>     Documentation updated. Test cases added.
>
>     git fetch https://github.com/x0id/otp.git jinterface_transport_factory
>
>     https://github.com/x0id/otp/compare/erlang:master...jinterface_transport_factory
>     https://github.com/x0id/otp/compare/erlang:master...jinterface_transport_factory.patch
>
>     Thanks.
>
>
>
>
>
>
>     _______________________________________________
>     erlang-patches mailing list
>     erlang-patches@REDACTED <mailto:erlang-patches@REDACTED>
>     http://erlang.org/mailman/listinfo/erlang-patches
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20150107/59a4b6bd/attachment.htm>