The (not too) recent changes to the LASTOUT index as regards POST requests are an enormous improvement for me.
Now, the last thing I am aware of that does not quite work the way I would like in the LASTOUT index are items like <http://localhost:8080/refresh-recurse/?url=http://www.pmsf.de/pub/cmucl/doc/cmu-user/;depth=5;limit=http://www.pmsf.de/pub/cmucl/doc/cmu-user/;images=Y;frames=Y> i.e., cases where the "outgoing" URL was actually an instruction for WWWOFFLE to fetch pages recursively. Selecting that link from the LASTOUT index does not have the desired effect of informing me about the pages that were fetched, and I have to remember the URL and search the LASTTIME index instead for these items. Would it be possible (with reasonable effort) to make sure that the LASTOUT index links to a page listing the new pages recursively fetched or something like that? I assume this information would be available by parsing the starting page and checking the LASTTIME index. (Ideally, one would then be able to sort pages as on the index pages. Or one might also present pages in a tree structure corresponding to the "generations" of the recursive fetch.) Alternatively, it would already be an improvement if selecting that link in the LASTOUT index led to a page stating that this links represents a recursive selection of items that can be reached starting from some URL (http://www.pmsf.de/pub/cmucl/doc/cmu-user/ in the above example) that is then linked to. Best regards, and thanks to Andrew for WWWOFFLE - Albert.
