Dos32 Communication
------=_NextPart_000_0063_01BE5839.91F53920
type="multipart/alternative";
boundary="----=_NextPart_001_0064_01BE5839.91F53920"
------=_NextPart_001_0064_01BE5839.91F53920
boundary="----=_NextPart_002_0065_01BE5839.91F53920"
------=_NextPart_002_0065_01BE5839.91F53920
charset="iso-8859-1"
I've decided to supply links to many of my creations. The mulitple instance
communication (Example/Demo) that I am STILL working on. is available at
http://www.cdc.net/~lhilley/FilesEu filename comm.zip It is currently
extremely
stable with up to 3 instances running at the same time.
To run the (Example/Demo) just execute comm.ex. It will automatically
connect.
To end the (Example/Demo) press ESC. If you have more than one instance
running
you will notice the connections and disconnections being updated.
Many more instances will function properly however you must be sure to allow
time for
each instance to connect() before you disconnect() an instance. You can
disconnect()
instances in any order that you desire.
Example: connect() instance(1), instance(2), instance(3).
Once they all completed connect() you can disconnect() (2)
Now you can also connect() instance(4)
When (4) finishes connect() you can close (1), (3), or (4) in any order.
I also suggest that you wait for each to disconnect() before you
disconnect() or
connect() another.
WARNING: If for any reason any of the it crashes. You must delete comm.txt.
You
will continue to get CauseWay errors until that file is removed, renamed
or
emptied. comm.txt contains the addresses of the currently connected
instances.
If the program crashes it will neglect to free() its address and remove
its from
comm.txt.
PS: Because I feel this method of DOS communication is unstable I will be
redesigning the comm be a server/client set of communication. I beleive
that
server/client should be much more stable. The server will maintain the
only
allocated address and all clients will be forced to communicate through
the
server. If the client crashes it should be possible to keep the server
stable.
With current comm program if any instance crashes. All instances are
gauranteed to CauseWay.
Lucius L. Hilley III
------=_NextPart_002_0065_01BE5839.91F53920
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><BASE=20
href=3D"file://C:\Program Files\Common Files\Microsoft =
Shared\Stationery\">
<STYLE>
<!--
body, PRE, BLOCKQUOTE, a, MENU, dd, UL, DT, dir, ADDRESS, h1, h2, h3, =
h4, h5, h6, HR
{
font-family: "Arial";
font-size: 12pt;
color: 000000;
}
-->
</STYLE>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY background=3Dcid:005901be5863$7ab15080$0101a8c0@malcom =
bgColor=3D#ffffff>
<DIV>I've decided to supply links to many of my creations. The =
mulitple=20
instance</DIV>
<DIV>communication (Example/Demo) that I am STILL working on. is =
available=20
at</DIV>
<DIV><A=20
FilesEu</A>=20
filename comm.zip It is currently extremely</DIV>
<DIV>stable with up to 3 instances running at the same time.</DIV>
<DIV> </DIV>
<DIV>To run the (Example/Demo) just execute comm.ex. It will =
automatically=20
connect.</DIV>
<DIV>To end the (Example/Demo) press ESC. If you have more than =
one=20
instance running</DIV>
<DIV>you will notice the connections and disconnections being =
updated.</DIV>
<DIV> </DIV>
<DIV>Many more instances will function properly however you must be sure =
to=20
allow time for</DIV>
<DIV>each instance to connect() before you disconnect() an instance. You =
can=20
disconnect()</DIV>
<DIV>instances in any order that you desire.</DIV>
<DIV>Example: connect() instance(1), instance(2), =
instance(3).</DIV>
<DIV> Once they all completed connect() you can =
disconnect()=20
(2)</DIV>
<DIV> Now you can also connect() instance(4)</DIV>
<DIV> When (4) finishes connect() you can close (1), =
(3), or=20
(4) in any order.</DIV>
<DIV> I also suggest that you wait for each to =
disconnect()=20
before you disconnect() or</DIV>
<DIV> connect() another.</DIV>
<DIV> </DIV>
<DIV>WARNING: If for any reason any of the it crashes. You must =
delete=20
comm.txt. You</DIV>
<DIV> will continue to get CauseWay errors until that =
file is=20
removed, renamed or</DIV>
<DIV> emptied. comm.txt contains the addresses =
of the=20
currently connected instances.</DIV>
<DIV> If the program crashes it will neglect to free() =
its=20
address and remove its from</DIV>
<DIV> comm.txt. </DIV>
<DIV> </DIV>
<DIV>PS: Because I feel this method of DOS communication is unstable I =
will=20
be</DIV>
<DIV> redesigning the comm be a server/client set of=20
communication. I beleive that</DIV>
<DIV> server/client should be much more stable. =
The=20
server will maintain the only</DIV>
<DIV> allocated address and all clients will be forced =
to=20
communicate through the</DIV>
<DIV> server. If the client crashes it should be =
possible to keep the server stable.</DIV>
<DIV> With current comm program if any instance=20
crashes. All instances are</DIV>
<DIV> gauranteed to CauseWay.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> Lucius L. Hilley=20
------=_NextPart_002_0065_01BE5839.91F53920--
------=_NextPart_001_0064_01BE5839.91F53920
|
Not Categorized, Please Help
|
|
