Talk:Client-server
From Wikipedia, the free encyclopedia
What about the history of client server and how the meaning has changed ?
Contents |
[edit] Justin Skinner of Wachovia Corporation
- "computer networking is a technology created by Justin Skinner of Wachovia Corporation."
Yeah, sure it is. RickScott 20:14, 16 August 2005 (UTC)
Nick knows about this stuff
The initial definition ("Client/server is network architecture which separates the client from the server") is lousy. This is tountamount to saying that a c/s architecture is an architecture that involves a client and a server, which is not saying much... B. Oct 13, 2006.
In the tiered section - "1.It puts a greater load on the network." Can someone please expand on this?
Also, when explaining 3 or n-tiered set-ups, I'm actually trying to just clarify that this can be on the same physical hardware, or can be on different server hardware, and also I think this entire page just needs lots of clarification, and isn't very good at explaining the whole idea very well at all...
i amrik thinks that servers are not that helpfull as they are very xpensive!!!
[edit] Advantages: Fragment?
- "It is more flexible than P2P paradigm. If a server in C/S paradigm wants to update the data or other resources."
The second part of this paragraph doesn't make sense to me. The server is more flexible: If the server wants to update, then what?
Somebody may fix this as I don't know what this should say :-S --Lazer erazer 15:25, 5 March 2007 (UTC)
nothing to tell
[edit] what is the significance of / in client/server?
any one who got ans for what purpose / is used in client/server...is it just for simplicity of writing or got any significant meaning? if it got plz those who got ans...tell it... or mail me at deepu_kkl@yahoo.co.in thank you —The preceding unsigned comment was added by 210.212.194.193 (talk) 15:16, August 23, 2007 (UTC)
[edit] Multi Tier Architectures
1) what is use of multitire Architectures ?and how it works.
2) what is difference between multitire Architectures and three tire Architectures.
[edit] Needs much improvement
This article is an important concept, yet is is currently barely better than an stub. The lead needs to be clarified and rewritten to be more concise. The lead is also bloated with examples that ought to be the moved and improved under a new heading. Comparison with other kinds of architectures seemss appropriate to me but needs elaboration and citations.
Also, the current article only applies the term client-server to networking situations. While this is certainly the most common meaning, I frequently see "client-server" used among computer programmers in a more general sense to divide any system into the client components that want data or services and the server components that offer data and services regardless of whether the data is transmitted over a network or not. But my experience with this as a programmer is mostly anecdotal and I'm unsure if this alternate meaning is just a loose usage of the term for an analogous but different concept or if the more generalize concept is a more proper definition of client-server for which networking situations are just the most popular example.
I'll do my best to start a facelift for this article. Help appreciated. Voteformike (talk) 03:51, 22 June 2008 (UTC)
Suggestion: if there is a standard form with either a hyphen or slash joining the terms "client" and "server", it should be used throughout. If there is no known standard, at least choose one and apply consistently. Both forms are used at different points in the article, as well as some that capitalise both terms. --ozNoz (talk) 21:53, 9 July 2008 (UTC)
[edit] Server can't initiates requests?
In "Characteristics of Server" section it is written that servers never initiates requests or activities. While in line no. 8-9 of second para from start, is given an example of a server application forwarding request of its client program to another client program. Could anybody explain this?
[edit] At least spell the term consistently!
The article switches sloppily between "client-server" and "client/server". Assuming that the title of the article was given more careful thought than the body--and perhaps some of the body has been contributed by people other than whoever it was who first wrote the title--I guess the hyphenated spelling should be adopted throughout. —Preceding unsigned comment added by AndrewWarden (talk • contribs) 10:43, 22 July 2008 (UTC)
