WHAT THE DIFFERENCE BETWEEN CLIENT and SERVER?
81287
In simple terms: \n\nA server is a powerful computer that serves, i.e. performs some sort of task, for other, usually smaller, computers attached to it via cables or phone lines. These smaller computers are called clients.\n\nHere's an example: When you're at home browing the web, your computer, or to be picky your browser software, is the client and it connects to a server via your phone line. When you want to view a web page or download a file, your computer (client) contacts the server and asks it to fetch the page or file and send it back to you. Simple.
171548
multiple client single server means, there is only one system has all softwares, printers, data storing spaces etc and so many users are also on there. the benefit of it, that all user can log on the another system that connect with it. and work on their softwares, printers etc.\n\nGood luck!!!!!!!!\nIf u got ur answer, then please give me 10 marks with choosing as best answer.
258001
Remoting is what you would want to use.  Your class that holds the shared data should inherit from MarshalByRefObject, the application that controls the variable would be the server, and the app that reads it is a client.  There's a pretty good sample in the link.
41057
Below are some simple examples of how to send "stream" data from a client and a server using the TIdTCPClient and TIdTCPServer components.  Each connection on the server is an item in the server's Binding property.  Hopefully this helps.\n\nprocedure SendFromClient(Client: TIdTCPClient; Value: string);\nvar\n  ssOut: TStringStream;\nbegin\n  ssOut := TStringStream.Create('This is a string stream.');\n  try\n    IdTCPClient1.WriteStream(ssOut);\n  finally\n    ssOut.Free;\n  end;\nend;\n\nprocedure SendFromServer(Server: TIdTCPSever; Stream: TStream);\nvar\n  Buffer: PChar;\nbegin\n  GetMem(Buffer, Stream.Size);\n  try\n    Stream.Write(Buffer[0], Stream.Size)\n    Server.Bindings[0].Send(Buffer[0], Length(Value) + 1, 0);\n  finally\n    FreeMem(Buffer, Stream.Size);\n  end;\nend;\n\nSorry, noticed a mistake...corrected.
146982
Back in the eighties when network equipment vendors first started to hawk their wares, the term client/server was used to conjure up a host of fancy capabilities offered by the new hardware. Today, client/server has a very specific meaning that has nothing to do with hardware at all. Even so, most folks still associate the term client with the physical computers they are using and the term server with some other physical computer to which they are connected. There's a glimmer of truth there, to be sure, but today client/server means much more.\n\nWe're going to cover the essentials of client/server computing. We'll define one-tier, two-tier, three-tier, and n-tier client/server program architectures; we'll explain the difference between a thin client and a fat client; and we'll discuss the middleware concept. But first, you need to understand a few things about general software architecture.\n\nMost application programs have three major layers. On top is the presentation layer, which provides the human/machine interaction (the user interface). The presentation layer handles input from the keyboard, mouse, or other device and output in the form of screen displays. In the middle is the application or business logic, the functionality that gives the application program its character. Application logic makes the difference between an order entry system and an inventory control system, for example; it is often called business logic because it contains the business rules that drive a given enterprise. The bottom layer provides the generalized services needed by the other layers, including such things as file services, print services, communications services, and, perhaps most important, database services.\n\nFor simplicity, we will confine this discussion just to those programs needing database services. That's what most architects first think of when they hear the term client/server, but the general rules apply to any kind of service.\n\nThe number of tiers in a client/server application is determined by how tightly or loosely the three program layers are integrated. A one-tier application is one in which the three program layers are tightly connected. In particular, the presentation layer has intimate and detailed knowledge of the database structure. The application layer is often interwoven with both the presentation layer and the services layer. All three layers, including the database engine, almost always run on the same computer.\n\nOne-tier applications are easy to design and write, especially with today's modern software tools. It's also possible to create a multiuser one-tier application by running the application on several PCs and having them share the database. The database can be stored either on one of the PCs (a peer solution) or on a file server. Note that each PC running the application has its own copy of the database engine; only the data is shared, not the database logic itself.\n\nMultiuser one-tier applications are okay until the number of users gets large. The problem is that all the database work is performed in each client. For example, if the program needs to list all clients with the last name of Smith, all the information (indexes and data records) needed to resolve that query to the database must be transferred over the network. For some complex queries, a significant amount of data must be examined, perhaps even the entire database. At a more technical level, it is difficult to manage independent database engines to be sure that no conflict arises when two clients attempt to access or update the same record. This is called the record-locking problem.\n\nThe solution for the performance and technical problems associated with multiuser one-tier programs is two-tier client/server architecture. This type of application is written in mostly the same way as a one-tier application, with the exception that the database service (engine) no longer runs with the client. Instead, it
323541
A server is a device (either a stand alone computer, or an application within one computer) that manages network resources.  This can be as simple as a print server, that allocates printing resources from different computers to a server that houses pages of websites.\n\nA router is a device that forwards data packets along networks. A router is connected to at least two networks, commonly two LANs (local area networks) or WANs (wide area networks) or a LAN and its ISP’s network. Routers are located at gateways, the places where two or more networks connect.\n\nA switch is a device that filters and forwards packets between LAN segments. Switches operate at the data link layer (layer 2) and sometimes the network layer (layer 3) of the OSI Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs.\n\nGenerally, in a home setting, you do not have either a stand alone router or a swich.  You have a modem (DSL or Cable) connected directly to the ethernet connection of your computer, or a built in dial up modem in the computer that utilizes a telephone line to transfer information.  If you have a wireless network at home, however, you most likely have a switch built into your wireless router.  Most home routers generally have four different ethernet connections that you can hook different computers to.  It is a switch that allows the router to have 4 connections.  In a larger setting, a switch is a seperate device.  The most commonly used switches are made by Cisco, and the typical switch has 24 connections.  Linksys is the division of Cisco that provides hardware to home users.  Even if you don't have the need for wireless networking or to connect several computers together, it is advisable to have a router between your modem and your computer, as the better home routers have built in firewalls that will in essence make your computer invisible to hackers searching for computers.
232339
Differences are that they are different clients software.  I use Limewire which is real good if you know what you are looking for and how to look out for it.
171625
Request.ServerVariables["REMOTE_ADDR"].ToString() \n\n\n"REMOTE_ADDR" is just string. It's built in.
536013
You cant access a server without logging on.\nEven if you are on a client computer and are trying to access it remotely you have to log on the server.\nIt is the safest computer in the network you are try to access DUDE!!!!!!!!!.
665972
An application server is a server computer in a computer network dedicated to running certain software applications. The term also refers to the software installed on such a computer to facilitate the serving (running) of other applications.\n\nApplication server products typically bundle middleware to enable applications to intercommunicate with various qualities of service — reliability, security, non-repudiation, and so on. Application servers also provide an API to programmers, so that they don't have to be concerned with the operating system or the huge array of interfaces required of a modern web-based application. Communication occurs through the web in the form of HTML and XML, as a link to various databases, and, quite often, as a link to systems and devices ranging from huge legacy applications to small information devices, such as an atomic clock or a home appliance.\n\nPortals are a very common application server mechanism by which organizations can manage information. They provide a single point of entry for all users, they can access Web services transparently from any device, and they are highly flexible. Portals can work inside or outside of the organization, and they can attach themselves to any part of it.\n\n\n\nThe term Web server can mean one of two things:\n\nA computer that is responsible for accepting HTTP requests from clients, which are known as Web browsers, and serving them Web pages, which are usually HTML documents and linked objects (images, etc.). \nA computer program that provides the functionality described in the first sense of the term\n\nAlthough Web server programs differ in detail, they all share some basic common features.\n\nHTTP responses to HTTP requests: every Web server program operates by accepting HTTP requests from the network, and providing an HTTP response to the requester. The HTTP response typically consists of an HTML document, but can also be a raw text file, an image, or some other type of document; if something bad is found in client request or while trying to serve the request, a Web server has to send an error response which may include some custom HTML or text messages to better explain the problem to human people (people trying to fetch a web page, etc.). \nLogging: usually Web servers have also the capability of logging some detailed information, about client requests and server responses, to log files; this allows the Webmaster to collect statistics by running log analyzers on log files. \nIn practice many Web servers implement the following features too.\n\nConfigurability of available features by configuration files or even by an external user interface. \nAuthentication, optional authorization request (request of user name and password) before allowing access to some or all kind of resources. \nHandling of not only static content (file content recorded in server's filesystem(s)) but of dynamic content too by supporting one or more related interfaces (SSI, CGI, SCGI, FastCGI, PHP, ASP, ASP .NET, Server API such as NSAPI, ISAPI, etc.). \nModule support, in order to allow the extension of server capabilities by adding or modifying software modules which are linked to the server software or that are dynamically loaded (on demand) by the core server. \nHTTPS support (by SSL or TLS) in order to allow secure (encrypted) connections to the server on the standard port 443 instead of usual port 80. \nContent compression (i.e. by gzip encoding) to reduce the size of the responses (to lower bandwidth usage, etc.). \nVirtual Host to serve many web sites using one IP address. \nLarge file support to be able to serve files whose size is greater than 2 GB on 32 bit OS. \nBandwidth throttling to limit the speed of responses in order to not saturate the network and to be able to serve more clients.
1108672
http://en.wikipedia.org/wiki/Server_%28computing%29
108097
If you use a server side scripting language, such as php, the code is running on the server and the result is passed to the www server in html format.\nIn case of client side scripting, such as javascript, the entire script code is downloading to the local machine and the browser interprets it.
192670
Most people think of it as software with a web-browser\ninterface and server-based computations.\n\nThere can be variations on that theme in that the UI\nmight be client-based Java or javascript (so that some\nof the computations are performed on the client).  But\nthe important distinction is that the user doesn't \nhave to buy/load/administer any client-side software.
433334
The role of a server is to provide services to clients. Examples: DHCP, Printer, Security, Application sharing, DNS, Web hosting, and the list goes on and on and on. Perhaps the best way to say it, is it allows you to have all these services with out having to actually put it on your own computer.
733693
Probably nothing that you don't already have. Just about any computer these days can function as a server. What exactly are you trying to do? Please let me know and I'll provide more specific info.
713943
The differences between Java and .NET is mostly of the syntax and libraries.\n\nBecause both of them work on same architectural concepts and frameworks.
343106
Thin Client:\nIn client/server applications, a client designed to be especially small so that the bulk of the data processing occurs on the server. \nAlthough the term thin client usually refers to software, it is increasingly used for computers, such as network computers and Net PCs, that are designed to serve as the clients for client/server architectures. A thin client is a network computer without a hard disk drive, whereas a fat client includes a disk drive.\nNetwork Computer:\nAs indictaed above, it has a hard-drive for locally loaded software (and OS) as well as a greater potential for processing power...