No. The server has no way of knowing what the client will do with the bits once it has received them.
In the case of PDF, I believe that the file can be flagged so that no fully-compliant PDF viewer will permit saving a copy, but it is easy enough to alter one of the open-source viewers to ignore that flag. Besides, the user might tell his browser to save rather than display, and then PDF features will not be involved at all. Or the "browser" might be something like wget or curl or libwww GET, which are designed specifically to fetch files without looking inside them. You could adjust your web server to refuse service to such agents -- if the agent has not been instructed to lie to the server about its identity, claiming it is (say) Firefox or IE. There are lots of things you can do, but none is really fully effective. The most you can do is raise obstacles for the determined user to step over. All of those obstacles can be overcome with very small effort. I would not take the trouble to raise them. It might be better to consider how you can provide a useful resource in such a way that it is not a big problem if someone saves a copy. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgp67RpV3DfVg.pgp
Description: PGP signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
