Thread: How to handle the Clients for Peer to Peer Connection at Server Side in Java

I am working on project which require peer to peer connection between multiple clients. Clients are Window and Android Applications. So far I am able to connect the Window and Android Application to the Server which accept the connection on two port one for Window and One for the Android. In this Project we require to send some file and other resources from window to android, when the android client request. I want to know whether it is a good practice to accept the connection from window on start-up and store the socket resources in Vector with Window Client Id, And when Android send the request for a particular window client then use that socket resource and connect window to android client, Or store the window IP and Port in Database, Create the connection to window when request came from Android. Which approach is better and how to achieve that. There may be 10L connection at the same time. I am developing all the three application(Android,Web and Window) in Java.[/B]

Welcome to the Forum! Please read this topic to learn how to post code correctly and other useful tips for newcomers.

Originally Posted by joginder89

I am working on project which require peer to peer connection between multiple clients. Clients are Window and Android Applications. So far I am able to connect the Window and Android Application to the Server which accept the connection on two port one for Window and One for the Android. In this Project we require to send some file and other resources from window to android, when the android client request. I want to know whether it is a good practice to accept the connection from window on start-up and store the socket resources in Vector with Window Client Id, And when Android send the request for a particular window client then use that socket resource and connect window to android client, Or store the window IP and Port in Database, Create the connection to window when request came from Android. Which approach is better and how to achieve that. There may be 10L connection at the same time. I am developing all the three application(Android,Web and Window) in Java.[/B]

Hello and welcome.

Im not sure if i understood you fully.

Clients are Window and Android Applications. So far I am able to connect the Window and Android Application to the Server which accept the connection on two port one for Window and One for the Android.

You talk about p2p connections yet you mention server. So could you clarify your topology a bit and explain purpose of each node?

I want to know whether it is a good practice to accept the connection from window on start-up and store the socket resources in Vector with Window Client Id, And when Android send the request for a particular window client then use that socket resource and connect window to android client, Or store the window IP and Port in Database, Create the connection to window when request came from Android.

If i got this right, you are asking if its better to store open connections in a vector and on demand use them for communication VS. having the connection parameters stored and use a new connection when needed?

If the above is right, i'd say it depends. It depends on the frequency of the needed connections. You don't want to store idle open connections for no good reason, plus you'd have to remember to close em. But if you need the connections frequently ( opening new connection cost > payload ) then it makes sense to store them somewhere.

Somewhere in the middle would be to store the connections and have a timeout on them and on each request check if there is already an open connection, if not, then create a new one.

There may be 10L connection at the same time.

What you mean by 10L ? 10 ?

Thats my 2 cents at least Sorry for the shoddy answer, maybe ill be able to give an stronger opinion after getting some more info

The person asked the question and then departed. Three years ago.

Please don't resurrect old posts. Although self advertising with links might be ok in the "Paid Java Projects", making a nuisance of itself in technical forums can only make your site look bad.