Is this best idea to use custom server application?

Question

1.00/5 (1 vote)

See more:

I need to transfer a data between client application for both pc and android through internet.So i need one server.

From client side,i need to poll the server whether it has data from another client.
If it has,i need to connect to server to retrieve the data.

For this i planned to use sockets because i can able to transfer lot of data in a single connection.

First i planned to use PHP sockets,But PHP sockets allow only one request at a time.
So then i planned to use Java Custom Server Application with SSL Socket.

To setup the server,i'm going to get VPS and execute the Java application in that vps.

Is this best idea?

Posted 16-Feb-15 20:02pm

cybersa

Updated 16-Feb-15 21:18pm

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 17-Feb-15 2:07am

Can you ever stop asking about nothing?
Are you going to create a server for the sake of creating server? Yes, what you want to do is find, but it all depends on your goals you don't bother sharing with us. Can you please stop wasting your and our time for nothing? First of all, re-posts are considered as abuse.
—SA

cybersa 17-Feb-15 2:51am

I already mentioned that

I have a client application for both pc and android.I need to connect this client app to sever for transferring of data between clients through internet.

Mohibur Rashid 17-Feb-15 3:06am

First of all, if you don't have a server already, why do you have client for both pc and android? By the way, you are not being detained. PHP socket has nothing to do with you description. What you need is a server that will transmit data. I would suggest you(as you seems learning) you better start with HTTP server. PHP will process your data and reply to your pc and android application. And remember HTTP server don't send request to client by its own. Client would have to beg and then server will respond. And please be more constructive with your question. I would request you to follow Sergey Alexdrvich Kryukov's Suggestion.

cybersa 17-Feb-15 3:18am

Ok.
I improved the question.

Mohibur Rashid 17-Feb-15 3:32am

As I said, any http server will do. Install apache, install php, cause they are free and do your thing, your client will have to request to http port, php will process the rest.

cybersa 17-Feb-15 3:38am

If im using PHP means,i need to poll the server many times.

For example.
If I send one request to client 2 from client 1,it takes some time to process the data and reply to client 1 through webserver.

Within that process,i need to poll the server whether the client 2 finished its job.

So i thought socket could be useful.

Mohibur Rashid 17-Feb-15 3:44am

When you are talking about socket, the answer is no. Cause you will have to develop a whole server for this. Which is not impossible. Certainly possible. But doing it with PHP is meaningless. Moreover I can't think a way of achieving this with PHP. HTTP server can handle more than one process at the same time. And there must have to be time delay for a client to pull data from server, otherwise your server will give up or fail.

cybersa 17-Feb-15 5:27am

My Idea:
Create a server with following feature.
1.Server accept the connection from the Client 1 and create a thread 1.(For Multiple Client Support)
2.Thread 1 -> Save request msg at database and keep the connection alive with client 1 for some time.
3.Thread 1 also poll the database for result of Client 2 until its timeout.

4.Client 2 poll the server for any request for it.
5.If any request,It will connect to server and create a Thread 2.
6.Client 2 send its processed data to thread 2.
7.Thread 2 save the result at database.

8.Now thread 1 can read the result at database and pass it to client 1.

Hope you can understand.

Sergey Alexandrovich Kryukov 17-Feb-15 11:02am

All right. A thread per client is a really bad idea. It would be is absolutely superfluous and could create too many threads. One thread for all clients is enough.
—SA

cybersa 17-Feb-15 11:10am

If i'm using Single Thread means,how can i handle the multiple client request simultaneously.

Sergey Alexandrovich Kryukov 17-Feb-15 11:30am

How did you manage to read "singe thread" from my comment?
Please see my answer.
Also, what did you mean by "simultaneously". What, you don't know special theory of relativity?
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-02-17T05:13:00

Please see my comments to the question.

Not only client per thread is too much, it is, at the same time, not enough. Server side needs at least two communication thread for two different purposes: one listens for new connection, another one sending/receiving data. Please see my past answers:
an amateur question in socket programming[^],
Multple clients from same port Number[^],
How Do I Get To Know If A A Tcp Connection Is Over[^].

Also, you mentioned "poll the server". Why polling the server "for any request"? The meaning of request is different; this is something which can be done at any time. But if you really need polling (to get to the moment of time when some activity is completed, typically), this is another bad idea. You need to understand that client-server model is a very bad, limiting model. Please see my past answer:Application 'dashboard' for website accounts[^].

Now, the bright side is: with sockets, you are not limited by the client-server. The server push mentioned in the post post referenced above can be easily implemented. For example, you can implement application-layer protocol implementing published-subscriber or its combination with client-server, or anything like that. Just note that you always implement some application-level protocol on top of the transport-layer protocol, even if you don't call it a protocol. So, it's better not to pretend you don't and do it explicitly. Naturally, this application-layer will be custom for a custom service (I would prefer call it "service", not "server" to avoid suggestive naming referring to pure client-server.) Please see:
http://en.wikipedia.org/wiki/Application_layer[^],
http://en.wikipedia.org/wiki/Transport_layer[^],
http://en.wikipedia.org/wiki/Transmission_Control_Protocol[^].

—SA