6 replies to this topic

[ElvisPr]

Hi.

This one is little cloudy question...

There is a server that is connected to another machine (Linux based).
The other machine needs to transfer short data (one line of text) to the server.

I can choose how the other machine will transfer this data.
What should I prefer?
TCP / HTTP / other... ?

I know details are missing but by guidance, I'll try to provide more.

Thanks.

[Matt Ellen]

what gets the job done in the least amount of work?

what protocol is the server listening for?

[ElvisPr]

How can I tell what is the server listening to?

I need to define how will the other machine will provide my server the data.
Will it send the data to me by TCP or any other protocol or in some other way.

My decision will be implemented on the other machine and I will have to get the data on my side.

Did I answer your questions?

[Matt Ellen]

If you are setting up the server then you will know which protocol the server is listening out for (raw TCP, HTTP, FTP, something else). Is your sever running software that is listening for your message? That software will be listening for a particular message, so that will tell you what protocol is best to use.

[ElvisPr]

I will need to implement the software that listen to the incoming message from the other machine.
The question is what will be the easiest to listen to?
Currently there is no such software for this matter.

[Matt Ellen]

so you are writing the sever and the client software?
TCP is error tolerant, I would use that since you're only transferring only line of text.

[sam_coder]

if the other machine needs to transfer data to the server, as just a line of text or whatever, there are so many ways you could do this.
So, if I get this straight, the server is windows, and the machine that needs to transfer data to is Linux based?

You can use sockets, and that may be the most efficient way to transport, but there are some things youd need to consider, such as the fact that you mentioned you want to transfer a line of text,
so you have text encoding, you also have byte ordering, as well as application life cycle. Presumably the server would have to bring up your listening application, and manage connections etc.

I personally would set up something more like a web service. in C#, you could implement this though web methods, or though Services (like WCF),

the nice thing about using web methods, or wcf services or anything like that, is most platforms will enable you to bind to them, leaving a lot of the low level stuff to your tools, and just allow you to focus on what you're trying to accomplish.

if your server is running windows (if I got that striaght), you can host such a thing in IIS, and that would manage the whole lifecycle.

anywho, just a thought