On 22-07-11 06:23, Peter Firmstone wrote:
You're right about allowing for local connection paths for TURN, I
wonder how we can tell we've got the right local subnet.
Indeed. You need an external identity for your exported endpoint usable
from the outside, and an internal identity for the insi
Sim IJskes - QCG wrote:
On 20-07-11 14:04, Peter Firmstone wrote:
The Endpoint implementations I'm interested in are the SSLEndpoint's.
The socket in the SslConnection class is connected with a
SocketAddress (in SslConnection.connectToSocketAddress)
So if you have created your own Socket wit
On 20-07-11 14:04, Peter Firmstone wrote:
The Endpoint implementations I'm interested in are the SSLEndpoint's.
The socket in the SslConnection class is connected with a SocketAddress
(in SslConnection.connectToSocketAddress). So if you have created your
own Socket with your own SocketFactory
Sim IJskes - QCG wrote:
On 19-07-11 02:35, Peter Firmstone wrote:
Uuid). The problem they ran into; the service and proxy needed to be
trust verified again after the connection was reestablished, but
permissions had already been granted. To make matters worse it was the
I think that we only re
On 19-07-11 02:35, Peter Firmstone wrote:
Uuid). The problem they ran into; the service and proxy needed to be
trust verified again after the connection was reestablished, but
permissions had already been granted. To make matters worse it was the
I think that we only reach an optimal trust situ
On 19-07-11 02:35, Peter Firmstone wrote:
If you take a look at TcpServerEndpoint.enumerateListenEndpoints where
the TcpEndpoint is created (or fetched) for export, where it is
serialized. You will see there that the endpoint description consists
of host, port and socketFactory.
In the TcpEndpo
Sim IJskes - QCG wrote:
On 18-07-11 14:07, Peter Firmstone wrote:
Sim IJskes - QCG wrote:
On 10-07-11 06:37, Peter wrote:
Any suggestions, ideas or assistance is welcome.
A ServerEndpoint needs to know its external contact identity. In case
of the TcpServerEndpoint the hostname where the cli
On 18-07-11 14:07, Peter Firmstone wrote:
Sim IJskes - QCG wrote:
On 10-07-11 06:37, Peter wrote:
Any suggestions, ideas or assistance is welcome.
A ServerEndpoint needs to know its external contact identity. In case
of the TcpServerEndpoint the hostname where the client needs to
connect to.
Sim IJskes - QCG wrote:
On 10-07-11 06:37, Peter wrote:
Any suggestions, ideas or assistance is welcome.
A ServerEndpoint needs to know its external contact identity. In case
of the TcpServerEndpoint the hostname where the client needs to
connect to.
Correct, that would be the publicly vis
On 10-07-11 06:37, Peter wrote:
Any suggestions, ideas or assistance is welcome.
A ServerEndpoint needs to know its external contact identity. In case of
the TcpServerEndpoint the hostname where the client needs to connect to.
A ServerEndpoint behind a NAT probably has a private net address/
10 matches
Mail list logo
