As far as I can tell, the ns_sets are being used exclusively by specific
threads, so the data shouldn't really be going from one ns_set to another,
except that it does happen, so I'm thinking there might be something
happening with the ns_set implementation.
I'll look into the possibility of using nsvs.
On Tuesday, September 25, 2012 1:23:44 PM UTC+8, Jeff Rogers wrote:
ns_sets are not internally interlocked. If you are using the same
shared set in multiple threads, you need to protect it with a mutex.
Do you specifically need the indexability of ns_sets? nsvs are easier to
use for most cases, and if you have more than a few keys probably faster
too.
-J
Sep Ng wrote:
I have several ns_set objects in my aolserver with the persist flag on
to manage several things but I'm noticing that some of the ns_set
objects are losing keys for no apparent reason. Also at one instance,
the ns_set object retrieved belongs to a totally different one. I'm not
sure if there's a bug with ns_set or if there's something wrong with my
code, but I thought I'd throw this one out there to see if you guys have
experienced this issue before.
Thanks in advance.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
aolserver-talk mailing list
aolserv...@lists.sourceforge.net javascript:
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk