RendezVousService is one of 6 JXTA standard services.
All JXTA standard services are using pipe (a unidirectional, unreliable message delivery mechanism) to do the necessary communication with each other. Here handling incoming messages can be done based on poling-model or controlled by associated listeners.
Iâ€™m wondering that Rdv and its clients can have a time out - featured communication link!
How it is possible?
1. - Can a user configure the JXSE so, that JXSE uses TCP or BiDiPipe (instead UDP) to deliver its 6 standard services to myAPP?
2. - Why your Rdv and clients must use TCP to communicate?
After a more precise look at log - report, it seems, that the caller of close() uses different available ports for different actions BUT within the same â€œcommunication-sessionâ€ as following:
188.8.131.52:[b]1540[/b] vs. 184.108.40.206:[b]4981[/b]
220.127.116.11:[b]3508[/b] vs. 18.104.22.168:[b]3506[/b]
Is it (also, maybe) the cause for failed close-operation, reported often in other forumâ€™s threads or at mailing list?
What happens, if you change the source code of [b]net.jxta.impl.endpoint.tcp.TcpConnection.close[/b] (TcpConnection.java:[b]696[/b]) so that assigned available IO-port is used for all actions (sending message to Rdv and close the socket, and also other operations, if anyâ€¦)?
1. I have some edge peers, all of them can't reach each other dirrecly as they are in different networks behind firewalls. And I have one public rdv peer. For beeing able to send message from one peer to other peer I should
- at first connect to RDV
- and then create Socket conncetion between peers.
if a peer is disconnected from RDV I'll not have an ability to create socket connection to it.
2. I've used TCP protocol as it works more stable and quickly. maybe I'm worng with that. can you advise which protocol is better?
3 I'll try to experiment with source code
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.