Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <018e01c2123d$503f83c0$6132bc3e@BABEL> From: "Conrad Scott" To: "egor duda" Cc: References: <091e01c2120f$25e50290$6132bc3e AT BABEL> <1149904301 DOT 20020612194520 AT logos-m DOT ru> <00f201c21234$4e19d3b0$6132bc3e AT BABEL> <17816532682 DOT 20020612213549 AT logos-m DOT ru> Subject: Re: DuplicateHandle() question Date: Wed, 12 Jun 2002 19:16:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Egor, You wrote: > All server has to do is to return valid handle on success and 0 on > error. It's up to client to interpret the results. Or you can make > server return all handles in some structure so that client will have > to call server only once. But then again, all server has to do is to > fill this structure and it's up to client to discard all valid handles > if at least one of returned handles is 0. Okay, that's much the conclusion I was coming to but I wanted to make sure I wasn't missing something. Yes: the client calls the server just once and it returns a structure containing several handles. I was just trying to localise the error handling at the server end but I'll follow your advice here: if the return code (in the structure) indicates an error, the client will have to go through it and close any valid handles in it. Thanks for the input. // Conrad