It is actually saving the user of bandwidth because he only need to load the script once into the cookie, when caching of the page is off.

It may be a more complicated to use compared to regular placing of javascript, but it is more secure, because the regular script stealer isn't interested in doing alot of work getting the complete script. So if you have stored the script into one or more cookies depending on the size of your script, then you have cloaked your script away from the webpage, where everyone looks for the scripts. Here many newbies/script rippers fall off because they lack the knowledge to know where the script are hidden.

Even many experienced webdevelopers would not bother to put togheter a script that is put into multiple cookies.

My point by posting this was that there is many ways to secure your scripts from being stolen.
If you have a cool new script you want to protect a little this is a possible way.

It can also be smart to have field validation in this cookie so people can't at firsthand see how you check your form fields for abuse.

Another way to protect your scripts, or combined with this is to use the browsers No cache methods in the Meta tags, and also set a session variable that tells if the page is loading or not, if the page is loading the script is allowed to be loaded, as a src="/script/myscript.js" not included in the html page.

Drunk: Server side scripting is not possible to use on the client side, this are scripts that does e.g dynamic user interactions on a page, maybe a javascript menu or something like that.
It is very easy to steals/rip off scripts nowadays, so this is just another way to protect your client scripts.

Many people have used other methods, like putting alot of whitespaces to get the script long away.

I don't say this is the best most efficient way, but it is better than having the code in the html file.

I just like fumbling around with new ideas.

Do you guys think this can be used to load scripts into a cookie and then be able to run/execute this scripts from the local area zone in internet explorer, then you will be able to silenty load programs into a clients machine, or run already available programs on the clients machine, pretty scary if that works.