QUOTE(nigglesnush85 @ Mar 30 2008, 05:02 PM)

Thats a good point, No one method is absolutely foolproof, I suppose making a lot of the information severside using php, or inserting some javascript to protect content could hinder someones attempts slightly.
PHP can mask the backend stuff, but as for your other content (like test, images, etc.) it won't do much.
Javascript is too easily defeated to be much of a hinderance. For example, some web sites use javascript to prevent right-clicks; I can get around this by disabling javascript altogether, using an addon like NoScript (which I do), or by instructing Firefox to prohibit webpages from altering or disabling the contect menu.
The long and short of it, like groovicus said, is that once the page is loaded in someone's browser they have you content already downloaded to their PC. The WWW paradigm makes no provisions for digital rights protection whatsoever.
Further, obfuscation (like encrypting the source code) can have negative consequences. People with visual handicaps who use screen reading software, for example, may be unable to use your website if their screen reader uses a page's source code. And even from a more broad usability standpoint it's a bad idea.
Take a look at all the major websites out their. Google, Yahoo, Digg, Bleeping Computer, etc. None of them have any obvious protection against people downloading any part of their web presence. All the proprietary stuff is handled at the backend, where it should be, and users don't even know it's there.
The best steps I can recommend is having a clear and strong Terms of Use policy and enforce it vigorously. Don't go nuts, though, like these poor saps did:
http://pubcit.typepad.com/clpblog/2007/10/...ereby-agre.html