AOLserver Chat Logs

2008/05/10

IRC [01:06] *** Mooooooo parted the chat.
IRC [11:31] *** ryan-g2 joined the chat.
IRC [12:03] *** MichasServer joined the chat.
IRC [12:03] *** MichasServer parted the chat.
IRC [14:19] <ryan-g2> when is it a good idea to use thread-shared vars instead of a database?
IRC [15:14] *** Mooooooo joined the chat.
IRC [15:31] <CIA-51> 03mooooooo * 10aolserver/nsperm/nsperm.c: Fixed bug with netmask parsing
IRC [15:32] <Mooooooo> whoa, now that is just spiffy
IRC [17:51] *** Mooooooo parted the chat.
IRC [18:46] *** Mooooooo joined the chat.
IRC [19:15] <Dossy> Mooooooo: yeah, the CIA bot is very cool. I long for the day that folks complain about it because the chat is getting too much commit traffic. :-)
IRC [19:16] <Mooooooo> hehe
IRC [19:16] <Dossy> ryan-g2: when to use thread-shared vars. vs. database? when high concurrency/low latency is required.
IRC [19:16] <Mooooooo> first one ive seen in a long time
IRC [19:16] <ryan-g2> Dossy: can you give me an example?
IRC [19:17] <Dossy> Mooooooo: yeah, commits are few and far between these days.
IRC [19:18] <ryan-g2> I'm trying to maintain a list of locked objects, and I wonder whether I should do this in the db or with nsvs. The locking will only be a few seconds so I suppose it requires low latency.
IRC [19:18] <Dossy> what are you maintaining locks for? "objects" stored in the database?
IRC [19:18] <Dossy> I'd advise against using NSV in this case because it won't work when you have multiple frontend webservers.
IRC [19:21] <Mooooooo> ive been wondering for a few days... when I create a new ns_set in an adp, it is released at the end or does it stick around until the interp is gone?
IRC [19:22] <Mooooooo> or must it specifically be freed
IRC [19:22] <Dossy> It should be cleaned up by ns_cleanup, at the end of the request, IIRC.
IRC [19:23] <Mooooooo> ive never looked down that deep before, but good to know :)
IRC [19:23] <ryan-g2> ok, thanks Dossy
IRC [19:25] <Dossy> Mooooooo: yeah - it's probably worth reading over ns_cleanup once in a while, just to refresh the memory.
IRC [19:26] <Mooooooo> everything has been so stable for the last few years that i have barely looked at any code
IRC [19:33] <Dossy> heh, yeah :)
IRC [19:34] <Dossy> that's why I love it, too
IRC [19:44] <Mooooooo> was talking that over with my co-worker the other day. he's a LAMP/Drupal man and spends way too much time trying to keep everything updated
IRC [19:44] <Mooooooo> i got one server with 2 years uptime
IRC [19:44] <Mooooooo> haven't had to touch the install since the day after 4.0.10 was out
IRC [19:58] <Dossy> *nod* Yeah. It's hard to get any attention unless you're updating every two weeks, esp. with "critical security fixes"
IRC [20:04] <Dossy> It's also tough to decide what to "change" about AOLserver--there's lots of small things that could use improving, but anyone who's been using AOLserver even remotely seriously has their own library of procs to take the rough edges off. And, everyone likes doing that slightly differently ...
IRC [20:36] <Mooooooo> yeah, i really can't see what needs changing
IRC [20:37] <Mooooooo> i decided to redo the /NS/Admin stuff over again
IRC [20:37] <Mooooooo> but as adp's
IRC [20:38] <Mooooooo> first time ive edited the code in 8 years
IRC [21:15] *** ryan-g2 parted the chat.
IRC [21:44] *** holymoly joined the chat.