[ previous ]
[ Abstract ]
[ Copyright Notice ]
[ Contents ]
[ next ]
Smart Cache Manual
Chapter 14 Future
Smart Cache is now nearly finished and I hope, that there are no fatal bugs
left. I did not get any fatal bug report in SC .40, only some people reports
problems, which are caused by wrong configuration or misunderstanding; SC needs
a better documentation, so I updated this manual.
Next versions will have:
-
(sure) Look at Expire: header and try some new methods of
eliminating them without producing bad side-efects with caching pages. Use
special time in refresh_pattern for fine-tuning Expire ignoring?
-
(sure) When browsing offline, allow marking pages for later download.
-
Try to better integrate with my web grabber 'Smart Cache Loader'.
-
GC will use real directory size (if host OS reports it)
-
Workaround for Java dns caching bug, I have some ideas, but need some LAN/Inet
for testing...
-
(maybe) Redirect with more than one * (it allows make Redirects like
*redir.cgi?* -> http://*)
-
(maybe) support for multiple parent proxies. Who really needs this?
-
(maybe) Internal support for FTP protocol. Parsing of FTP server LIST replies
is a small problem. Why there are not standardized?
-
(not worth of programming effort) auto support for HTTP-resume on aborted
download; aborted downloads are now deleted. Web pages are quite short <
100K, so it does not make sense. For bigger or batch downloads use special
programs which handles this better; for example, my Download Machine or wget.
-
(never) Auto run Garbage collection. Have you ever heard something about cron?
-
(never) GUI. Slows down things a lot. Smart Cache must not depends on
graphics engine (Presentation Manager, X11, ..).
-
(never) C/C++/Objective C version. Java works fine for me.
-
(never) non
Open Source
version.
[ previous ]
[ Abstract ]
[ Copyright Notice ]
[ Contents ]
[ next ]
Smart Cache Manual
0.49.1
Radim Kolar hsn@cybermail.net