explain the definitions of server client mode?
85472
Client/server describes the relationship between two computer programs in which one program, the client, makes a service request from another program, the server, which fulfills the request. Although the client/server idea can be used by programs within a single computer, it is a more important idea in a network. In a network, the client/server model provides a convenient way to interconnect programs that are distributed efficiently across different locations. Computer transactions using the client/server model are very common. For example, to check your bank account from your computer, a client program in your computer forwards your request to a server program at the bank. That program may in turn forward the request to its own client program that sends a request to a database server at another bank computer to retrieve your account balance. The balance is returned back to the bank data client, which in turn serves it back to the client in your personal computer, which displays the information for you. \nThe client/server model has become one of the central ideas of network computing. Most business applications being written today use the client/server model. So does the Internet's main program, TCP/IP. In marketing, the term has been used to distinguish distributed computing by smaller dispersed computers from the "monolithic" centralized computing of mainframe computers. But this distinction has largely disappeared as mainframes and their applications have also turned to the client/server model and become part of network computing. \n\nIn the usual client/server model, one server, sometimes called a daemon, is activated and awaits client requests. Typically, multiple client programs share the services of a common server program. Both client programs and server programs are often part of a larger program or application. Relative to the Internet, your Web browser is a client program that requests services (the sending of Web pages or files) from a Web server (which technically is called a Hypertext Transport Protocol or HTTP server) in another computer somewhere on the Internet. Similarly, your computer with TCP/IP installed allows you to make client requests for files from File Transfer Protocol (FTP) servers in other computers on the Internet.
554297
http://www.webopedia.com/TERM/W/Web_server.html\n\nhttp://en.wikipedia.org/wiki/Special:Search?search=web+server&fulltext=Search\n\nhttp://computer.howstuffworks.com/web-server.htm\n\nhttp://www.aprelium.com/data/doc/2/abyssws-freebsd-doc-html/howdowswork.html\n\nhttp://www.thewhir.com/find/web-hosts/articles/webserver.cfm\n\nhttp://www.webopedia.com/DidYouKnow/Internet/2003/HowWebServersWork.asp\n\nhttp://httpd.apache.org/docs/1.3/misc/FAQ.html\n\n\n\nAs for the comment ""about web servers how I wouid"...think about this for a moment.....you want to know about web servers but you have no basic english skills?.....give me a break.."\n\nIf you read it as whole and not "about web servers how I wouid" it makes sense as reading "I want to know about web servers how I wouid learn better.?"
171625
Request.ServerVariables["REMOTE_ADDR"].ToString() \n\n\n"REMOTE_ADDR" is just string. It's built in.
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.
459876
A COM is a component.  Components are pre Active X for a client side program to integrate with a server side "component".  ASP integrates into this on the server side to display information.\nMy source is an example of passing an array through these components.
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...
627862
phillip, if you don't know what you're talking about, don't talk.\nThere IS no difference.\nSee, a web server is USUALLY considered an HTTP or FTP server, ie. something most browsers can see.\nbut technically, any kind of proces which opens a certain port and listens to in on a machine is a server...A web server.\nWell, that given it's tunning on TCP/IP, otherwise it's another type of server...Like an Apple Sever, for example.
862233
Let me understand the question, you want to know what kind of work goes on, at the server side of a network, right ?\nA server is the main person in the network. Anything & everything that is being worked on in network, has to pass through a server. A Server helps to co-ordinate every task with the back end. Now every application has a front end & a back end. Front end is what is visible to the end user and back end is what stores all the data, all the files, and helps in bridging the systems. Server also provides security to the data by not allowing end users to modify it without the admin's consent. I hope this answers your question...\nhttp://www.microsoft.com/windowsserver2003/sbs/serverinfo/default.mspx
614778
You can run the two servers simulataneously, but you have to configure them so that they use different port numbers. (i.e. IIS and Apache can't run *IN THE SAME TIME* if they were assigned the same port number like port number 80 for example)
368443
#A server program is a program that runs on a server machine while a client program runs on a client machine.
874883
admin status is the one what we configure on port.\nif we disable port using shutdown command, then its status will be administratively down, if we enable back it will be administratively up.\n\nComing to Protocol status, it shows wether connection from the other end to which this device is connected is working or not.\n\nProtocol down means either remote end is admin down or there is something wrong in the link :-)\n\nI hope I answered your question. :-) rate it..!!!\n\nCheers.
20157
depends on what you mean by *server* and what you want it to do.  Very few ordinary people will need a server, however if all you want to do is sharing files between two or more computers, you can add a hard drive to one of your computers and "share" which is possible in both Windows and Linux as relatively simple operations.\n\nOne thing to make sure is that you should never turn off the power to your *server* as it would stop serving.   If that troubles you you can buy out-of-the-box "network disks" or "network storage" which are in fact a small computer with a disk drive attached.\n\nFor more complex server configurations such as email servers, or web servers for web pages you are better of trying to establish what your internet service provider is offering.
629393
Two-tier architecture is a client/server architecture , where a request to do some task is sent to the server and the server responds by performing the task.\n\nThree-tier or a multi tier architecture  has client, server and database. Where the client request is sent to the server and the server in turn sends the request to the database. The database sends back the information/data required to the server which inturn sends it to the client.\n\nIn a modern two-tier architecture, the server holds both the application and the data. The application resides on the server rather than the client, probably because the server will have more processing power and disk space than the PC.\n\nIn a three-tier architecture, the data and applications are split onto seperate servers, with the server-side distributed between a database server and an application server. The client is a front end, simply requesting and displaying data. Reason being that each server will be dedicated to processing either data or application requests, hence a more manageable system and less contention for resources will occur\n\n\nCheers mate
239207
check how you are sendign the request.\npost / get\nsee if your sever is running properly.
717695
Explain? I guess that's not very specific. anyways the following URL should help\n\nhttp://www.danhendricks.com/code/ASP/Database%20Connectivity%20in%20ASP/
2728
It's really easy, you just have to use the Socket class in the System.Net namespace.\nPlease see a complete sample on the link below.
790793
This is a multi-threaded server.  Much like a web server could do.\nFor comparison, the previous slide is a single threaded server.\n\nThe loops you are interested in are act as such.\nThe server starts and waits for a connection request from a client.  (Upper right yellow box).\nNext: Someone (like you or me) starts our client application (browser) which connects to the awaiting server.  (Dotted line that enters under the upper right yellow box).\nWhen the accept(...) happens, server creates a 'socket' (not shown).  This server fork() 's off (creates) a thread (process) [center right yellow box] that accepts the socket (not shown) and uses the socket to open an input and output channel which connects to the client (not shown).  This whole thing is generally a very fast operation.  That action is done for this client, so it loops waiting for another client to connect.\n\nBack to the client.  Remember, the last thing the client did was connect to the server.  Now the client wants to make a request (write() ) to the server for information.  This is the left yellow box.  It 'requests' and the server 'read()' the request.  Processes it, write() the response back to the client which read()'s the message and does what it needs to do.\n\nThe Client yellow box, and lower Server (client server) yellow box keep repeating (that's the loops) until the client is finished with all its requests.  A good client may send a 'bye' message to the server, so it can cleanly exit.  Other times just having the client exit, drops the I/O connection to the Server thread, which recognizes that action as the client exited, and that server thread exists.\n\nHope this helps.\n=mike