At 14:49 10-03-00 , RHessel281(at)aol.com wrote:
>Can anyone give me an example of why someone 
>would want to use a server-side 
>imagemap rather than client-side.  Thanks.

There are three reasons I might suggest off hand... 

... Client-side image maps do not support all the features available with
server-side image maps.... if you need the features missing from
client-side maps, then server-side might be the way to go.

... Client-side image maps have closed (pre-defined) in features, while
server-side image maps are open... you can add additional features as your
needs might require. [pulling a example out of the air, perhaps allowing
shapes to be defined via bezier curves]

... Some initial client-side implementations were broken (such as Netscape
Navigator's partial implementation). So if you needed the full capabilities
of client-side image maps, and cared that they worked correctly for
everybody, server-side was the only way to go. [now, a few years later,
this is likely an at most incidental concern... unless of course the CEO of
your client just happens to have a PC at home with the old browser that
happens to yield unsatisfying results, wink.

In addition, one also has the option of using _both_ (I do for one client).
The reason for doing so would be to support both browsers that support and
those that don't support client-side image maps. Again, mostly of
historical concern [e.g. in code from several years ago] but quite possibly
of continuing concern, possibly in some niche situations.

Safe computing,  /Harold
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Harold A. Driscoll                 mailto:Harold(at)Driscoll.Chi.IL.US
#include <std/disclaimer>                 http://Driscoll.Chi.IL.US

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA