Re: [jinterface] transport factory implementation

Vlad Dumitrescu <[email protected]> Tue, 6 Jan 2015 17:07:12 +0100
Newsgroups gmane.comp.lang.erlang.patches
Message-ID <CAA-EFXvmFuL4NTNnpiyPVTPYtGhKKBF45LCjAs_asRK3zaBnWw@mail.gmail.com>
--===============7033714737261413826==
Content-Type: multipart/alternative; boundary=f46d043be1b02d58f5050bfe013f

--f46d043be1b02d58f5050bfe013f
Content-Type: text/plain; charset=UTF-8

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 <
[email protected]> 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
> [email protected]
> http://erlang.org/mailman/listinfo/erlang-patches
>

--f46d043be1b02d58f5050bfe013f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi!<div><br></div><div>Thanks for this. I will look closer=
 at the code in the next days. My first comment is that I think there shoul=
d 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 wo=
rk is that the Erlang nodes and epmd support and use that transport method =
too?</div><div><br></div><div>best regards,<br></div><div>Vlad</div><div><b=
r></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Sun, Jan 4, 2015 at 7:02 PM, Dmitriy Kargapolov <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">dmitriy.kargap=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tran=
sport factory basic implementation added. This makes possible<br>
creating connections between nodes using ssh channels or ssl.<br>
Default transport factory based on standart Socket/ServerSocket<br>
classes is provided. Modifications are backward compatible.<br>
Custom transport factory may be specified using 2 ways - via<br>
system property or defining special tuner class.<br>
Documentation updated. Test cases added.<br>
<br>
git fetch <a href=3D"https://github.com/x0id/otp.git" target=3D"_blank">htt=
ps://github.com/x0id/otp.git</a> jinterface_transport_factory<br>
<br>
<a href=3D"https://github.com/x0id/otp/compare/erlang:master...jinterface_t=
ransport_factory" target=3D"_blank">https://github.com/x0id/otp/compare/erl=
ang:master...jinterface_transport_factory</a><br>
<a href=3D"https://github.com/x0id/otp/compare/erlang:master...jinterface_t=
ransport_factory.patch" target=3D"_blank">https://github.com/x0id/otp/compa=
re/erlang:master...jinterface_transport_factory.patch</a><br>
<br>
Thanks.<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
erlang-patches mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><=
br>
<a href=3D"http://erlang.org/mailman/listinfo/erlang-patches" target=3D"_bl=
ank">http://erlang.org/mailman/listinfo/erlang-patches</a><br>
</blockquote></div><br></div>

--f46d043be1b02d58f5050bfe013f--

--===============7033714737261413826==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
erlang-patches mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-patches

--===============7033714737261413826==--