Implementing Client-Server

[rbangar]

Hello all,
I want to implement simple client - server application using http.The application is stand alone application and not web application.
I don't want to use socket concept as it doesn't allows multiple client requests.
plz help me.

[Norm]

I don't want to use socket concept as it doesn't allows multiple client requests.

Please explain why you think this is true.

[rbangar]

I have read that SOCKET's are used for peer to peer(1 to 1) communication.
plz let me know if I am wrong.

[Norm]

I was considering ServerSocket and Socket as both being sockets. One is used by the server and the other by the client.
You can use them for peer to peer or client-server.

[rbangar]

Yes very true but the concern is whether server socket responds to multiple clients at a time??

[Norm]

Not at the same time, serially one after the other. I don't know what the delay between connect is, less than a millisecs? or how the underlying software queues incoming requests until the serversocket is available.

Each connect would be passed to a thread to handle. The limit on concurrent clients would be determined by how many threads you can have running concurrently.

[rbangar]

Is there any alternative to socket for this particular problem??
Using http get and post methods used in web applications.

[Norm]

The communications of data is handled by sockets. HTTP is a protocol that uses sockets.
The other choice is Datagrams. They use a more primitive type of socket without the care and tending of the TCP layer of software to keep packets in order and ensure delivery.

There are several code examples on the forum. Do a Search for ServerSocket to see some of them.

[rbangar]

Ok !! thank you norm.