OpenEuphoria

Fw: Dos32 Communication

• Posted by Lucius Hilley <lhilley at CDC.NET> Feb 14, 1999
• 443 views

------=_NextPart_000_0017_01BE5840.9AC05600
        type="text/plain";
        boundary="----=_NextPart_001_0018_01BE5840.9AC05600"


------=_NextPart_001_0018_01BE5840.9AC05600
        charset="iso-8859-1"


-----Original Message-----
From: Lucius Hilley <lhilley at cdc.net>
To: Euphoria <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Sunday, February 14, 1999 4:46 PM
Subject: Dos32 Communication


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_001_0018_01BE5840.9AC05600