Message-Id:	<m0xGNAZ-000S20C@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT edu DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
Organization:	INTI
To:	Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>, djgpp AT delorie DOT com
Date:	Wed, 1 Oct 1997 14:49:49 +0000
MIME-Version:	1.0
Subject:	Re: DJGPP, interprocess communication, and DPMI

Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz> wrote
> > > One way to differentiate between more processes could be to use the
> > > Virtual Machine ID (Int 2F, 1683h) - or use the getpid() function from
> > > libc.
> > I think it can be used, but the complexity is in the syncronization.
> > What if one of the process hangs while have the control of the
> > channel?, I guess here we need a time out. What if one process is
> > too busy to answer ... etc.
> 
> This could probably be handled by the driver (via IOCTL calls). In 
> another posting, Eli mentioned the problem of multiple processes 
> attempting to use the buffer for communication; maybe something like 
> IP (as in TCP/IP) could be used, maybe port numbers (all the 
> addresses would be 127.0.0.0 anyway (or is that 128?)).  I've 
> recently been considering putting in support for the windows 
> instancing protocol so the driver can have process local data (eg 
> timeouts, IP ports etc).

My example uses packets similar to network ones, seems that here the solution 
is use the channel as a Level 0 layer of a net.
Another thing Michael have some problems to get TB working under W95, any 
idea?, your own TSR works.

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

- Raw text -