Homework question, this is a long answer.
Write and run a client and a server program in C-language using UDP
*language
Both the client and the server create a socket, but only the server binds the socket to a local endpoint. The server can then subsequently do a blocking readcall in which it waits for incoming data from any client. Likewise, after creating the socket, the client simply does a blocking call to write data to the server. There is no need to close a connection.
no,i want answer from your side
All of us (or most of us) would have started programming in Java with the ever famous "Hello World!" program. If you can recollect, we saved this file with a .java extension and later compiled the program using javac and then executed the class file with java. Apart from introducing you to the language basics, the point to be noted about this program is that - "It is a client side program". This means that you write, compile and also execute the program on a client machine (e.g. Your PC). No doubt, this is the easiest and fastest way to write, compile and execute programs. But, it has little practical significance when it comes to real world programming.
Server-base language mean code you write will be processed on server instead of client, ex: when you request a page from server (a php page) it will be first processed on server then server will send you result of codes.. it means you won't see php codes on the page only result of it.
Any code that remotely controls another computer is far from simple. The simplest method would be to write a client-server application, where the client runs as a service awaiting a shutdown instruction from the server. However, it goes without saying that a network administrator would take a dim view of employees remotely shutting down other employee's computers.
ofcourse we have server and clients first step is open the browser and write the domain name as www.google.com then we note the http is write that is meen the protocol http is commnected the server with client by use the ip address that are resolved by DNS
The easiest way to explain this is, as you suggest, by an example. So I'll give you an example. Let's suppose I'm going to write a piece of software that students at a school can use to find out what their current grade is in all their classes. I structure the program so that a database of grades resides on the server, and the application resides on the client (the computer the student is physically interacting with). When the student wants to know his grades, he manipulates my program (by clicking buttons, menu options, etc). The program fires off a query to the database, and the database responds with all the student's grades. Now my application uses all this data to calculate the student's grade, and displays it for him. This is an example of a 2-tier architecture. The two tiers are: 1. Data server: the database serves up data based on SQL queries submitted by the application. 2. Client application: the application on the client computer consumes the data and presents it in a readable format to the student. Now, this architecture is fine, if you've got a school with 50 students. But suppose the school has 10,000 students. Now we've got a problem. Why? Because every time a student queries the client application, the data server has to serve up large queries for the client application to manipulate. This is an enormous drain on network resources. So what do we do? We create a 3-tier architecture by inserting another program at the server level. We call this the server application. Now the client application no longer directly queries the database; it queries the server application, which in turn queries the data server. What is the advantage to this? Well, now when the student wants to know his final grade, the following happens: 1. The student asks the client application. 2. The client application asks the server application. 3. The server application queries the data server. 4. The data server serves up a recordset with all the student's grades. 5. The server application does all the calculations to determine the grade. 6. The server application serves up the final grade to the client application. 7. The client application displays the final grade for the student. It's a much longer process on paper, but in reality it's much faster. Why? Notice step 6. Instead of serving up an entire recordset of grades, which has to be passed over a network, the server application is serving up a single number, which is a tiny amount of network traffic in comparison. There are other advantages to the 3-tier architecture, but that at least gives you a general idea of how it works. Incidentally, this website is a 3-tier application. The client application is your web browser. The server application is the ASP code which queries the database (the third tier) for the question-and-answer you requested. I hope that helps! ANKUR MISHRA
Absolutely. All you actually need is a text editing program to write your code and a server to host it.
Norman E. Smith has written: 'Object-oriented programming using Turbo C++' -- subject(s): C++ (Computer program language), Object-oriented programming (Computer science), Turbo C++ 'Write your own programming language using C++' -- subject(s): C++ (Computer program language), Application software 'Practical guide to intranet client-server applications using the Web' -- subject(s): Intranets (Computer networks), Client/server computing, World Wide Web 'Developer's guide to HP printers' -- subject(s): HP LaserJet printers
How to write a termination letter of our services to a client due to no response