protecting code
- Started
- Last post
- 17 Responses
- seed
Does it bother you that if you work on a site and someone else takes it over later on in the future for whatever reason that they could take your code?
The idea of some noob or frontpage hack taking taking CSS files, server side code or worse a whole CMS admin system and reusing it bothers me.
- Mimio0
Doesn't really bother me, unless it's a highly developed application.
- UndoUndo0
apart from SSI there inst much you can do about it. especially when its on the client css etc as you can just pull that out anyway.
I wouldn't worry about it
- fugged0
write really shitty code so no one can figure it out.
or obfuscate the shit out of it.
- seed0
I guess you could put in your contract that if anyone else works on it they are not allowed to use the code on any other project.
- digilee0
you work for a company? if so then it's their, not your, code anyway so there's nothing you can do.
if you're freelance, then that's another story.
generally I would put the code through one of those apps that mangles it up before handing it over.
- madirish0
if you are not iin support of, or developing for any open soure community, then you can always encrypt it while compressing the code. makes it fully functional yet encrypted from ever opening.
- ********0
Doesn't bother me... actually I do my best to keep my code clean so anyone can come in and understand it.
- seed0
Would you care for instance if someone took a whole admin CMS system and started selling it their clients? I'm also curious do you let them keep source files? Would you care if someone took fully functional movie clips without your permission and used them in their worK?
- madirish0
the person or group who is taking an entire CMS or admin tool and commercially reselling it, or the services to implimenet it has MUCH bigger issues than just that.
when it comes to source files, it is hard to drawn the line with code. with artwork i feel it is a case-by-case basis and if correct, they own it all. this should NEVER be an assumed thing though w/ any project.
i agree 100% w/ 'puter- author the cleanest code possible so others can adapt and evolve the project (or fix) at any time. it is a fundamental aspect to any community effort.
now, if you run an M$ shop, you are in the wrong thread....;)
- ********0
get used to it, it public
- seed0
What do you mean? It's public once you release the code to the client?
- rockonski0
information wants to be free.
- seed0
information wants to be free.
rockonski
(Nov 10 05, 10:57)When I think of it that way maybe I am starting to sound like the drummer of Metallica.
- seed0
Oh nevermind, JazX, you meant the info on how to do these things is public anyway. So anyone with some initiative can learn it.
- ********0
what you do is you get myAppServerName.com
you put all dynamic code up there in someRelevantFolder.
add iFrames to taste.
client wants someone else to take over the site?
certainly. No problem.
*clickety click ;)
- seed0
I think I might just do satin cards for now. btw, Does foil stamp and letterpress debossing show through on the opposite side?
- seed0
wrong thread