Cool, once you've got your ProxiedEndpoint, can I do the Serialized form
for you?
Cheers,
Peter.
Sim IJskes - QCG wrote:
Peter Firmstone wrote:
Ok sounds interesting, lets work together, we need both types of
functionality, one for scalibility and the other for reliability, if
NAT p2p TCP fails we need to fall back on a routing service.
I've a few notes:
interface TransportService
extends Remote
{
MsgBlock poll();
void send( MsgBlock mb );
}
This is to support bidirectional message flow. (think bosh).
class ProxiedEndpoint
implements Serializable
{
private SomeId id ;
private Endpoint transportEndpoint ;
ProxyEndpoint( SomeId id, Endpoint transportEndpoint )
{
...
}
}
This is for the implementation and registration.
interface ProxyServer
extends Remote
{
ProxiedEndpoint createEndpoint();
}
Gr. Sim
