On Wed, Oct 10, 2012 at 10:09 AM, Gustaf Neumann <neum...@wu.ac.at> wrote: > > Using a "_ns_set" capable of handling "-shared" which just calls > existing "ns_set" with the unlocked semantics would not work, > using a lock with for all "_ns_set" commands is not good either > without modifying the existing "ns_set" semantics (one should > not be able to access variables created by "_ns_set" from > "ns_set"). If we check for the shared flag in "ns_set", we are > essentially at the old "ns_set" implementation.
I was thinking that the 2 or 3 people in the world that need backward compatibility would load the nsshare module and then: rename _ns_set ns_set You wouldn't use them both, you just want your old code to work the way it did in 1999. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
