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: group name - for client and server ? From:Robert Lauriston <robert -at- lauriston -dot- com> To:Monique Semp <monique -dot- semp -at- earthlink -dot- net>, TechWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 10 Nov 2015 09:44:13 -0800
Those *sound* like two unrelated requirements. Out of context it's not
clear how they relate.
Whether there's a single noun that would include both servers and
clients is impossible to say without more information.
The first might be clearer as, "To integrate product A and product B,
use the same type of compiler flag on each, either prod_a_client and
prod_b_client, or prod_a_server and prod_b_server. If one is compiled
as a client and the other as a server, integration will fail."
On Mon, Nov 9, 2015 at 8:40 AM, Monique Semp <monique -dot- semp -at- earthlink -dot- net> wrote:
>... to integrate product A and product B, they must both be enabled as clients or both be enabled as servers (not one product as the client and the other product as the server), via the compiler flags (which are all independent: prod_a_client, prod_a_server, prod_b_client, prod_b_server).
> ... to integrate product A and product B, you must define the same <group-name> flag
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com