Zend / ionCube vs Dolphin

Hi guys in order to restrict my users fro view source code Im wandering to encrypt dolphion php files by zend or most likely ioncube. Does somebody of you guys have an experience with encrypting dolphin with ioncube ? I would like to know anbout performance drops anc compatibilty - can be dolphin ioncuve encoded. I was looking also for some free solution - maybe sopmebody can recommend me something same quality like ioncube but free ?

Any thoughts about dolphin encryption will be welcome as I have no experience in php encoding at all. Also now Im running dolphin on hostgator shared account...

nobody ?

Hellloooooo ...... nobody around ?

As long as your web server is setup correctly, and Dolphin has the proper file/directory permissions (as well as the .htaccess files functional), users cannot access the "raw" Dolphin files, such as for example, the actual join.php file. You do not need to encode/encrypt the contents of Dolphin's files.

Thanks magnussoft for reply. What about index.php ? As I checked about 10 dolphin sites including boonex demo I can see source code of index.php on every of sites incl boonex one. Can I also restrict access to source of index.php by proper setting of permissions/htaccess ? If yes will u be that friendly and tell me what to change ?

The source code that you see is html output after processing PHP.

IonCube's only used for server side encryption and decryption, and cannot be used directly on HTML output, because interpretation of the HTML source codes is up to your browser, and the server is no longer involved from this point on.

Therefore, your question is invalid.

I suggest that you save some time and effort and invest that somewhere else. No matter what encryption you use, there will always be easy decryption readily available online.

Flurmingo - I actually thought that its the way you just told :-( ... so there is not any way how to encode html output of php  or other way to restrict users from seeing that ?

Again, the encryption is totally useless.

I can always use Firebug to sniff the operations.

hmmm.....is there an other way than encryption how prevent users from view php hrml output in browsers or my intention simply CANT be done ?

It cannot be done, as the processed source code of the page in question must be sent to the web browser for it to display anything.

okz ...thanks alot guys for your expressions...now I know that it cannot be donne so I stop chasing this :-(