Accessibility
 
Home / Products / Support
Macromedia - Configuring Your Server for Macromedia Shockwave
The following instructions assume that you are already familiar with maintaining or administering a web server. If this isn't the case, you'll need to have your system administrator or ISP configure the server for you. While you are waiting for this to happen, you can include a parameter to your EMBED tags that will tell Netscape 3.0 or higher the MIME type of the EMBEDed file (see the list of MIME types below to find the one appropriate for your file). For example:

TYPE="application/x-director"
TYPE="image/x-freehand"

To configure your server:

1 In your web server documentation, look up configuring MIME types. When you've found the configuration file, simply apply the sample MIME type mappings listed below.
2 If your documentation isn't helping, try some online resources. One web resource that may be of use to you is Web Compare , where you will find a compilation of information about MIME configuration for all types of servers.
3 Contact the manufacturer of your web server software for technical support. hey should have FAQs and advice about how to configure their web server software for your operating system. Links to several popular server software net sites are:

Netscape
NCSA
WebSTAR

An HTTP server must be configured to recognize and handle shocked media. The server's MIME types file must be updated to include the appropriate MIME type lines.

Director MIME type mappings
AddType application/x-director dir
AddType application/x-director dcr
AddType application/x-director dxr

Note: To configure your server for Audio, use the above Director MIME Type mappings.

Authorware MIME type mappings
AddType application/x-authorware-map aam
AddType application/x-authorware-seg aas
AddType application/x-authorware-bin aab

FreeHand MIME type mappings
AddType image/x-freehand fh4
AddType image/x-freehand fh7
AddType image/x-freehand fh5
AddType image/x-freehand fhc
AddType image/x-freehand fh

Flash MIME type mappings
AddType application/futuresplash spl
AddType application/x-shockwave-flash swf

The format of the MIME Type directive will change from server to server. For example, on an NCSA server, the server administrator updates the srm.conf file to include the appropriate MIME Type lines.

On some servers, you can combine the types into one line:

AddType application/x-director dir,dcr,dxr,fgd

On others, you may need to specify the extension with a period:

AddType application/x-director .dir

On Netscape servers, the entries are in the file mime.types and they're formatted like this:

type=application/x-director exts=dir,fgd,dxr,dcr type=image/x-freehand exts=fh4,fh5,fh7,fhc,fh type=application/x-authorware-map exts=aam type=application/x-authorware-seg exts=aas type=application/x-authorware-bin exts=aab

Once the file is updated the server usually needs to be restarted.

Configuring MIME types on a per-directory basis
Some web servers allow override files on a per-directory basis as an alternative to changing the configuration for the entire server. For example, if your Internet service provider (ISP) doesn't add the Shockwave MIME types to its server, as a user you could create a file to add the MIME types in your personal web directory. On an NCSA server, this file is called

.htaccess , and the format is the same as for srm.conf in the MIME type mappings directives above.

Linking to www.macromedia.com
To let users download the appropriate plug-in, you should provide a button that links to the Shockwave Download Center. There is a Made With Macromedia page that explains this process and provides buttons that you should use.

Downloading considerations
Multimedia delivered over the Internet is limited in size, primarily because the majority of users dial in at relatively slow speeds--14,400 or 28,800 bits per second. At 14,400 bps, a user receives only about 1400 data bytes per second. At 28,800 bps the rate increases to approximately 2800 bytes per second. At these speeds, it takes 30 seconds to one minute to download a 60,000 byte file.

If there is heavy traffic at the internet access point, on the Internet host, or if there's network congestion, the rate drops even lower--to as low as a few hundred bytes per second. For now, it is a good idea to assume your files will download at a rate of about 1000 bytes per second.

Delivery speed limits the size of files because most users will wait only a brief time for a file to download. Within the next few years, new technologies will dramatically increase access speeds to the internet. As the new technologies become widely available, the limits imposed by the current technology will no longer be an issue. You'll be able to deliver CD-ROM size--and larger--files in real time across the internet. For now, ask yourself:

Will the user be willing to wait for the file to download?
Is there any way to reduce the size of the file to shorten the time the user has to wait before play begins?

The chart below shows theoretical throughput times for modems of different speeds. The speeds 14,400 and 28,800 bps are common for modems, 64kbps and 128 kbps is the throughput of an ISDN line, 1.5 mbps is the throughput of a standard high speed internet connection (T1).

Download Times at Common Modem Speeds
Content Size 14.4 kbps 28.8 kbps 64 kbps 1.5 mbps
Small graphics & animation 30 K 30 secs 10 secs 6 secs 1 sec.
Small complete movie 100-200 K 100-200 secs. 50-100 secs. 20-40 secs. 1 sec.
Short video clip 500 K 500 secs. 120-240 secs. 90 secs. 3 secs.
Full-size movie 1 MB N.A. 256 180 secs. 6 secs.
MPEG video stream -- N.A. N.A. N.A. Continuous
[an error occurred while processing this directive]