* Reply to msg originally in C++
 
-=> Quoting Christian Andersen to Danial Gibson <=-
 
 CA> Hello Danial.
 CA> 
 CA> 16 Apr 97 09:25, Danial Gibson wrote to Christian Andersen:
 
 DG>  Back onto mailslots. I was doing what you said (get every 2nd
 DG> message), and it worked. Until I sent two message together (ie, send
 DG> one message then send another immediately after - no pause), and for
 DG> the first message, it only sent it once. So this method doesn't work
 DG> _all_ the time. So I came up with a better idea. When you send each
 DG> message, add a packetnumber to the front. Then, when you receive a
 DG> message, check if this packetnumber is >= the last packetnumber. If it
 DG> is, discard the
 DG> message. It's more complicated to implement, but at works all the time
 DG> (as far as I can tell).
 
    Probably a little out my league here, and don't know much about Win95.
 It appears to me that each msg pkt sent through the pipe is terminated
 with a dup of the last msg (Ie. msg(a), msg(b), msg(c), msg(c)). This would
 allow an app a bi-sync pipe area that could use error checking if needed,
 or ignored if not.
    You might want to check to see if that holds true through several
 consecutive reads.
 
    Sorry Mr. Moderator if I'm a bit off topic here. Promise to try to keep
 things relative. :)
 
___ Blue Wave/QWK v2.20 [NR]
--- TriToss (tm) Professional 10.0 - #246
---------------