 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | reply to ssj4android
Re: This is alarming said by ssj4android:I know how TCP and UDP work, I just don't know what to consider a "server" (I like precise definitions). My logic is TCP requires one node (the server) to listen for a connection and another node (the client) to initiate the connection. But perhaps that's a faulty definition, as which node was the listening one is irrelevant in, say, bittorrent. The purest example of a p2p paradigm I can think of is a multicast chat program, where one node doesn't know and doesn't care how many other nodes are on the network. You are observing that most servers listen for incoming connections -- but that's common, not definitive. Who makes the connection and who listens is more of a function of how the end-points set up the communication channel, but client-server has more to do with centralization of actual work or resources.
To illustrate that it's the processing that is the chief consideration, consider the X-Server which connects outbound to X-client programs but since the terminal does the graphics processing, it is the server to the client applicaitons.
Here's one definition: »www.sei.cmu.edu/str/descriptions···ver.html
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More fun, more features, Join BroadbandReports.com, it's free...
|
