Re: Protecting source code

2006-08-25 Thread Tim Pushor
Danny Brian wrote: It will always be true that a dedicated hacker will be able to decompile, dump opcodes, or otherwise reverse engineer the work of another, regardless of the language or file format. But the value of compiling a program is not so much its security, but its illusion of securit

Re: Persisting data across authenticate <-> authorize ?

2004-12-13 Thread Tim Pushor
Perrin, Perrin Harkins wrote: Anything with individual TTL settings per item will let you do this. Right - I scoured the Cache::FastmMap perldoc and didn't see any way to do this. It doesn't normally go to disk with BerkeleyDB. There's a shared memory cache. Even things that just use the fil

Re: Persisting data across authenticate <-> authorize ?

2004-12-13 Thread Tim Pushor
Perrin, Perrin Harkins wrote: Could I not just set a global variable in my authentication handler that the authorization handler can then access? Yes, but it will persist between requests. If you put it in pnotes, it will get cleared automatically, even if your code dies while processing a

Re: Persisting data across authenticate <-> authorize ?

2004-12-10 Thread Tim Pushor
Perrin Harkins wrote: Hi Tim, Welcome to mod_perl! Thanks Perrin! I would like to cache this information somehow so that the authorization handler doesn't need to perform these operations over. Put it in $r->pnotes() and it will be available in later phases. Could I not just set a g

Persisting data across authenticate <-> authorize ?

2004-12-10 Thread Tim Pushor
Hi modperl list First of all, I am so excited to have discovered mod_perl. I have been writing modules in C for a while now, and have been porting an old module that used to work under Apache 1.2 to work on Apache 1.3 and am having trouble for various reasons. I picked up mod_perl and in less t