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.
On Wed, Jun 27, 2012 at 7:00 AM, McLauchlan, Kevin <
Kevin -dot- McLauchlan -at- safenet-inc -dot- com> wrote:
> If it is the server that reaches out to the "clients", tells them when to
> wake up, causes them to display what it wants them to display, demands
> input from the lowly user/operator/customer on the server's
> schedule-or-whim, and is generally in control of the whole show, then I
> might concede that you have found a "server/client" arrangement. Treasure
> it. It's likely more rare than hen's teeth.
> If it's the clients that connect and make demands of the server, with
> which the server attempts to comply, then you are describing a
> client/server relationship, just like every other frikken' client/server
> relationship in the known universe.
> Tell 'im I said so.
I concur. Most of the time the server runs processes initiated by "a"
client, if not "the current" client.
Regardless, it doesn't matter, because the architecture itself is
Client/Server. User docs are written for users, not machines. The server
won't be offended to be in position subservient to the user. The server
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.