Blame | Letzte Änderung | Log anzeigen | RSS feed
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-iso-8859-1"><LINK REL="Start" HREF="index.html"><LINK REL="Contents" HREF="toc.html"><LINK REL="Prev" HREF="63UsingthecachewithClientSideImageMaps.html"><LINK REL="Next" HREF="65Commonfeatureforallgraphs.html"><STYLE TYPE="text/css"><!--BODY { font-family: serif }H1 { font-family: sans-serif }H2 { font-family: sans-serif }H3 { font-family: sans-serif }H4 { font-family: sans-serif }H5 { font-family: sans-serif }H6 { font-family: sans-serif }SUB { font-size: smaller }SUP { font-size: smaller }PRE { font-family: monospace }A { text-decoration: none }--></STYLE></HEAD><BODY><A HREF="toc.html">Contents</A><A HREF="63UsingthecachewithClientSideImageMaps.html">Previous</A><A HREF="65Commonfeatureforallgraphs.html">Next</A><HR NOSHADE><H2><A NAME="6_4">6.4 Some final comments</A></H2><P></P><UL><LI>If you want the timeout value to be "forever" then you can specify a0 as the timeout value (or leave the parameter blank). To regeneratethe image you will have to remove the image files from the cache. Thisremoval could for example be handled by a nightly cron-job</LI><LI> If you use images where you have enabled the anti-aliasing youshould strongly consider using caching since anti-aliasing is quitetime consuming compared to standard line drawings.</LI></UL><P></P><HR NOSHADE><A HREF="toc.html">Contents</A><A HREF="63UsingthecachewithClientSideImageMaps.html">Previous</A><A HREF="65Commonfeatureforallgraphs.html">Next</A></BODY></HTML>