delorie.com/archives/browse.cgi | search |
From: | Ludvig Larsson <ludvig AT club-internet DOT fr> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: [Semi-OT] Making a transaction. |
Date: | Tue, 23 Feb 1999 02:07:08 +0100 |
Organization: | Faas-Goldhart |
Lines: | 18 |
Message-ID: | <36D1FF3C.1D60@club-internet.fr> |
References: | <3 DOT 0 DOT 6 DOT 32 DOT 19990212180944 DOT 0089a1a0 AT pop DOT netaddress DOT com> <36D0BFD4 DOT 7235 AT club-internet DOT fr> |
NNTP-Posting-Host: | toulouse-4-58.club-internet.fr |
Mime-Version: | 1.0 |
X-Trace: | front6.grolier.fr 919731825 16290 194.158.125.58 (23 Feb 1999 01:03:45 GMT) |
NNTP-Posting-Date: | 23 Feb 1999 01:03:45 GMT |
X-Mailer: | Mozilla 3.01C-CLUB (Win95; I) |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I thought about it, and maybe you should opt for a master-slave system instead: a) is mastar and decides if things have been done correct. b) does what it's been told, and replies. If a) won't get any answers, it has to relance a question about what went wrong and decide to redo or abort. If both a) and b) can decide weither things have been going ok, I think a lot op questions/answers has to be sended, and maybe a) and b) might decide different things anyway if there are problems with the last transfer. Ludvig Larsson
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |