TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Client/Server vs. Server/Client From:Gene Kim-Eng <techwr -at- genek -dot- com> To:"Bruce Megan (ST-CO/ENS2.5-NA)" <Megan -dot- Bruce -at- us -dot- bosch -dot- com> Date:Tue, 26 Jun 2012 14:58:09 -0700
What I like to do in cases like this is line up someone in Marketing who
will say that they're marketing the product or system as whatever I know it
is supposed to be and that whatever the engineering or technical reasoning
is for calling it something else, what it is going to be called is what the
customer has been primed to expect by our marketing.
If it happens that Marketing is fine with whatever the engineers want, then
I just save my energies for some other windmill.
Gene Kim-Eng
On Tue, Jun 26, 2012 at 12:53 PM, Bruce Megan (ST-CO/ENS2.5-NA) <
Megan -dot- Bruce -at- us -dot- bosch -dot- com> wrote:
> Hello All:
> I have an engineer that insists on calling this a Server/Client System. Is
> there any difference between Client/Server and Server/Client?
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.