Please read the History section for information on changes 
and bug-fixes.

AMarquee is a system for broadcasting information between Amigas and JVMs.  It
uses a server-hub information storage model, where any Amiga program or
JAVA application may upload information to the central server, and other
Amiga programs or JAVA-applications may download it.

Information is stored on the server in a filesystem-like 
structure, with each client given its own "directory" in the tree.  Each 
client may read or write to its own directory on the server, and may read 
the directories of the other clients (assuming they allow it access).

The AMarquee system was designed in such a way that "polling" of 
information to detect updates should never be necessary.  Instead, 
each client may subscribe to a set of entries in the server, and 
whenever the subscribed data is updated, the client will be notified 
of the change.  This technique helps keep bandwidth usage as low as
possible.

As alternatives to the information-storage model, AMarquee
features a message-passing model and a direct-connect model.  You may
easily pass data messages to other clients, through the 
AMarquee server, or connect directly to other AMarquee clients and
send data straight to them, without bothering the server. In addition it is also possible
to connect to servers or clients without using the AMarquee protocol by using the QNewSocketSession()
functions.

Also, the AMarquee system is heavily multithreaded.  A client-side
thread is started in the background for each connection made with
amarquee.library, and a new server thread is created on the server
for each connection received.  This multithreading allows the user
program to do other things while data is being sent or received,
and avoids bottlenecks on the server computer.  The multithreading
is completely transparent to the user program.  Furthermore, with 
amarquee.library, no socket programming knowledge is necessary.
All the user's code needs to do is make amarquee.library calls and 
Wait() on a supplied Exec-style MsgPort for data.

Lastly, both the AMarquee client code and the AMarqueed server code
are re-entrant, to minimize memory usage.