RE: Client/Server vs. Server/Client

["Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>]

Follow-up: I just noticed that lots of Google's "server/client" results aren't for that literal string (I hate that they don't respect quotes regarding punctuation). They're for things like SQL Server client, Terminal Server client, etc. So the preference for "client/server" is probably much stronger than the Google results suggest. 

> -----Original Message-----
> From: techwr-l-bounces+richard -dot- combs=polycom -dot- com -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+richard -dot- combs=polycom -dot- com -at- lists -dot- techwr-l -dot- com]
> On Behalf Of Combs, Richard
> Sent: Tuesday, June 26, 2012 2:39 PM
> To: Bruce Megan (ST-CO/ENS2.5-NA); techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Client/Server vs. Server/Client
> 
> Bruce Megan wrote:
> 
> > I have an engineer that insists on calling this a Server/Client
> System.
> > Is there any difference between Client/Server and Server/Client?
> 
> He can call it what he wants -- it's a mostly free country.
> 
> Or is he insisting that _you_ call it that, too? If so, is he your
> manager or the owner of the doc, or just a SME?
> 
> Google "client/server" (with quotes) and get 22.6 million results.
> Google "server/client" (with quotes) and get 6.4 million.
> 
> So if this engineer is telling you that you should use the latter, you
> can reply that you're going to stick with the industry-standard usage
> that most people know and understand, and back it up with those
> numbers. :-)
> 
> Richard G. Combs
> Senior Technical Writer
> Polycom, Inc.
> richardDOTcombs AT polycomDOTcom
> 303-223-5111
> ------
> rgcombs AT gmailDOTcom
> 303-903-6372
> ------
> 
> 
> 
> 
> 
> 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Create and publish documentation through multiple channels with Doc-To-
> Help. Choose your authoring formats and get any output you may need.
> 
> Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
> 
> http://bit.ly/doc-to-help
> 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> You are currently subscribed to TECHWR-L as richard -dot- combs -at- polycom -dot- com -dot- 
> 
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> 
> 
> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources
> and info.
> 
> Looking for articles on Technical Communications?  Head over to our
> online magazine at http://techwhirl.com
> 
> Looking for the archived Techwr-l email discussions?  Search our public
> email archives @ http://techwr-l.com/archives

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives