"not copied" is impossible. If your concern is code protection then you have to look at code protection problems and solutions and not at file management or DCC client solutions.
Use of compiled files only (Python binary compiles are trivial to reverse but they will be pretty annoying to read and rip as the interpreter strips off a lot of crud) and the such. If your concern is pollution (people writing crap in it) just make sure the filer end of things is properly managed. User groups and such. How that's done is almost entirely dependent on what solutions you use for storage and file management over there. On Tue, Jul 9, 2013 at 8:22 PM, Martin <furik...@gmail.com> wrote: > Hi list, > > This isn't exactly an SI question but I was wondering if there is any way > to limit direct access to a SI Workgroup allocated in a server so it could > be used by SI, but not copied or altered. > > Martin > -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
