Name Value
HEADER Multimedia Technical Overview
 When using an imaging workstations, a user can view images that are linked
 The network transmission works by sending a message first.  During the
 exchange of message protocol data units, information is exchanged about
 the [BLOB] that is going to be sent via FTP.  The sender indicates that
 there is a BLOB to send.  The receiver replies with the IP address to 
 send the message to and the directory to put it in.  The sender then
 constructs a series of commands that will access the FTP software
 running on that machine, stores in as a file that can be executed in
 batch mode and puts an entry MUMPS global to indicate that the file needs
 to be executed.  A background process in MUMPS (XMRTCP), polls this file
 every few seconds and when it sees an entry, it makes a request to the
 to a message on a second screen.  This works using standard calls to the
 imaging API to move the appropriate image into the export directory.  
 When the image is in the export directory the aforementioned file is
 executed and the image is FTP'd to receiver of the message.  
 API of the imaging product.  Images are brought off of a file server on
 the local area network via ethernet and displayed.  Network transmissions 
 of messages are performed from a platform that has both NFS capabilities
 and TCP/IP.  Images are delivered off of the file server that is on the
 local area network into a directory that is mounted via NFS onto this 
 platform, again by a call to the imaging API.  The relationships of
 multimedia [HARDWARE] must be setup correctly.
DATE ENTERED 1993-12-06 20:30:00