Don't know if I'm replying to this properly, so forgive me if I'm not.
* To solve the bandwidth issue, I'll just limit the final delivered
* file size to be something like 300k instead, regardless of link depth used
* in the template. If your fetched content is larger than 300k, it just won't
* deliver it, and will return you an error message instead. Would that help?
I understand limiting the depth level to two (2). To work around it, I am just going one deeper into the site (past the usual index, as in the USA Today site, for example). The limiting to 300k sounds great. If that would be the case would you be extending the link depth to a higher # so that as long as it was under 300k it would process it? If that would consume too much bandwidth, I understand your rationale for not doing so.
* If the zip returned doesn't "drag it to the desktop", perhaps it's
* empty? What happens when you double-click on the zip? Are there any files
* inside it?
As for getting the documents back that don't drag to the desktop, they aren't empty. I can go to web-mail and download the file there. When I do though, it says that there isn't an app to handle it and it displays a long # as the file name. To remedy this, I just click the "Save File AS" (using MS Explorer). The file then downloads as a zip file with the name I assign to it. This doesn't happen with all of them - probably 1 out of 10/15 attempts. The others drag to the desktop fine. I am using Mac OS X.1.5, the built-in Mail app and MS Explorer for these purposes. It really isn't a problem to access the trouble files via webmail, just wanted to pose the question.
I have received the error messages when I mistype a url, etc.
Again, thanks for PLER.
bh
_______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
