Hello guys, anyone playing with client and server socket using C or other programming languages?

Any text file or links to share?

Do I need to simulate a local DNS to experiment on client / server scenario?

Thank you.

My favorite guide Beej's Guide to Network Programming. Contains plenty of examples.

Suggest you use the web search string "client server socket example in C"

You do not need to simulate a local DNS unless you wish to use hostnames. If you use direct IP addressing, you can just client-server away.

Note that client-server can mean many things.

Are you interested in BSD socket programming and the programming in C for Linux or System-V?

Are you interesting in client-server "application" level programming where it uses communications channels, but is architect such that you have a client user which needs to contact a server for centralized data or access?

Things like UDP are sometimes called connectionless because you don't need to "connect" the socket, or you still can perform this action.

Meanwhile TCP you are required to do actions like connect and listen, and these exact examples are what I'm talking about when I mention a web search.

1 members found this post helpful.

Start with simple IP-based sockets where the computer simply connects to itself. Learn about the "select()" call where a computer waits for an incoming connection request, and see what it does to respond. Create another program which tries to connect to it and send, of course, "Hello, World!".

Start by grabbing any example anywhere – in your favorite language – study it, and watch it go.

1 members found this post helpful.

Hi Rmistler, thanks for this: "You do not need to simulate a local DNS unless you wish to use hostnames. If you use direct IP addressing, you can just client-server away."

Yes, DNS is just for hostnames. Sometimes, we think too much ans forget basic things. LOL.

Thanks Sundialsvcs, I want to use C program.

1 members found this post helpful.

For C code, I reiterate the recommendation to refer to Beej's guide. It contains the exact examples you are seeking in code, as well as explains them.

1 members found this post helpful.

Thanks Rtmistler, yes it looks a good link. It has the basics.

Lol, never know about this site: "http://lmgtfy.com"

I couldn't resist. But also, "when the world really is chock-full of examples," it also goes to show that you don't have to imagine that you're starting from scratch on some kind of voyage-of-discovery. Grab something that someone has already done and shamelessly steal from it.

In this case, especially look for "high-level frameworks." Look for someone who has already built(!) the "low-level plumbing" that you imagine that you must now build.

Always remember, today, that "virtually anything that you think that you 'have to write'" has already been written – and it's out there, waiting for you to find it.

Hello guys, sorry for being naive in sockets.
I was surprised for client and server sockets.

If a client application is already listening from the server application, there is no need for authentication.

The client will do what is programmed to do, by the server app.

Could you please explain this?

Just a quick overview, an example.

Server program:
It will connect to port 5689, with IP Address of course.
Once connected to port 5689, tell client to display something or execute anything.
Server needs to know the IP Address of the client.

Client program:
Client program must be running.
Client will listen to port 5689.
Once it detects a connection and it knows that it is from the server program.
The client will display, like. "Hello, i'm connected. I own the system"

5689 has to be open if you're doing the testing behind firewall.
But worst if the program is listening on port 80,53 or 443 which is basically open on all networks.

I would say you swapped words 'client' and 'server'

And I guess that it bears repeating ... "do not do a thing already done!"

For instance, surf to https://github.com and search for "linux client server socket example."

Or, how about "client server engine."

Don't waste your time, these days, "figuring out" something, when today you can in a matter of a few seconds lay your hands on a working example ... or a complete prototype that you can quickly adapt to your specific purposes. We have very(!) much to thank the generous people who have given us, free of charge, the product of their ... so that we don't have to do the same.

1 members found this post helpful.