Using AMarqueed - the serverAMarqueed is the "server" portion of the AMarquee system. Its job is to act as the client program's "proxy" or representative on the server computer. It stores data that the client uploads, and returns data that the client has requested, either directly or in response to "subscribed" data having been changed. Note that there's no Java version of this yet. You have to connect to an Amiga having AMarqueed installed to test your programs. A suitable one is located at qamitrack.tibb.at, port 2957. For your information it's possible to configure the server with the following environmental variables. - AMARQUEED_MAXMEM If set, the value of this variable will be taken as the maximum number of kilobytes each daemon is allowed to allocate. For example, typing "setenv AMARQUEED_MAXMEM 45" limits each connection to allocating no more than 45K of memory for data storage. /P> - AMARQUEED_MINFREE If set, the value of this variable will be taken as the size of a "safety buffer" of free memory. No AMarqueed process will be able to allocate more memory unless at least this much free memory exists in the system. For example, entering "setenv AMARQUEED_MINFREE 100" ensures that AMarqueed processes will never use up the last 100K of system memory. - AMARQUEED_MAXCONN If set, this variable determines the maximum number of simultaneous connections that will be allowed from any given host. This can be used to prevent any one computer from "hogging" the server's capacity. - AMARQUEED_TOTALMAXCONN If set, this variable determines the maximum number of simultaneous AMarqueed connections allowed. For example, entering "setenv AMARQUEED_TOTALMAXCONN 5" will ensure that there are never more than 5 AMarqueed processes running at once. - AMARQUEED_PRIORITY If you wish the AMarqueed server tasks to run at a particular priority, you can set this variable to the priority you want them to run at. If this is not set, AMarqueed daemons will run at the priority AmiTCP launches them with (-10 on my system). - AMARQUEED_PINGRATE In order to keep the shared data tree free of clutter, AMarqueed makes sure each client is still there by sending it an empty transaction every so often. While these transactions are transparent to user programs, they do have a slight impact on network and CPU usage. This ENV variable allows you to set the number of minutes of idle time that will elapse before a null transaction is sent. For example, setting AMARQUEED_PINGRATE to 5 will cause a null transaction be sent to each client after 5 minutes of idle time. Then, if the client has not responded to the transaction within 5 more minutes, it will be removed from the system. The default rate is every 3 minutes. - AMARQUEED_DEBUG If set, each AMarqueed session will open a debug console on startup, showing various state information. [Note that you must do something like "setenv AMARQUEED_DEBUG 1" for this to take effect, just entering "setenv AMARQUEED_DEBUG" won't do it.] - AMARQUEED_FAKECLIENT This option may be set to a host/program name path (e.g. "/fakehost/fakeprogram", in which case the AMarquee server will attempt to give incoming connections this designation instead of their actual one. This feature allows you to easily simulate connections from various hosts when debugging an AMarquee program. It should not be set during normal use. - AMARQUEED_MAXQUEUEDMESSAGES This option allows you to set a limit on the number of (internal) messages that an AMarqueed client may have pending at any one time. If an AMarqueed daemon exceeds this limit, it will immediately quit and disconnect its client. This is useful in situations where some clients are connecting over TCP connections that are too slow or lossy to carry the amount of data they are being sent by other clients. When this happens, their server daemon's outgoing message queue can grow quite large, unless you limit it with this variable. The default setting is unlimited. If you do set this variable, it's a good idea to set it to at least 50, so that clients aren't knocked off too easily.
|