Re: [AOLSERVER] Scoping in AOLserver TCL

Rob Mayoff wrote: +-- On Sep 5, Mike Hoegeman said: you can clean up things when a connection ends using the ns_atclose command. e.g. In this case, it's a lot safer for Brian to use namespace delete ::whatever at the top of the procedure that sets the namespace variables. That

Re: [AOLSERVER] Scoping in AOLserver TCL

That's what I am doing! I have to say though that my code's readability has deteriorated somewhat. It was bad enough having things like: eval set SumX $$SumName when I wanted SumX to be either Sum1 or Sum2 etc.. now I've replaced it with: eval set SumX \$::ba_ns::$SumName Yack! Cheers, Brian

Re: [AOLSERVER] AOLserver Chat recommen

Of course, an IRC server is simple enough to set up on any machine -- I can gladly host it on my box. It's not like IRC is a high-bandwidth service... My two bits. Michael Kriston Rehberg wrote: Unfortunately, most of these IRC servers immediately reject people coming in from .aol.com

Re: [AOLSERVER] connsperthread

I have a form that is generated from a query result set, and in each record, there is a select widget which is, in turn, generated from a query result set. I can't run the inner query until the outer query is exhausted, so I need 2 handles, I think! Personally, I think I would run the first

Re: [AOLSERVER] connsperthread

Ian Harding wrote: [05/Sep/2001:14:08:54][19325.21][-conn2-] Error: dbinit: db handle limit exceeded: thread already owns 1 handle from pool 'pgpool' [05/Sep/2001:14:08:54][19325.21][-conn2-] Error: could not allocate 1 handle from pool pgpool I believe you probably did something like this:

Re: [AOLSERVER] connsperthread

At 03:06 PM 9/5/01, you wrote: I thought about that, but other than style, is there any advantage to one technique over the other? Database connections aren't free, but neither are lists and arrays... I believe that's your measure of memory and cpu and slashdots. You probably have a lot more

[AOLSERVER] [ aolserver-Bugs-458929 ] Ns_Set implementation and null bytes

Bugs item #458929, was opened at 2001-09-05 15:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=458929group_id=3152 Category: Architecture: Server (nsd) Group: aolserver3_4 Status: Open Resolution: None Priority: 5 Submitted By: Adam Zell (zellster)

Re: [AOLSERVER] connsperthread

Err. Methinks you are right. I have a form that is generated from a query result set, and in each record, there is a select widget which is, in turn, generated from a query result set. I can't run the inner query until the outer query is exhausted, so I need 2 handles, I think! Ian A.

Re: [AOLSERVER] connsperthread

That makes sense. Sorry for the noise... Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 09/05/01 02:37PM You are seeing this error because you have to allocate both DB handles in 1 ns_Db call. This is to

Re: [AOLSERVER] connsperthread

I thought about that, but other than style, is there any advantage to one technique over the other? Database connections aren't free, but neither are lists and arrays... Thanks for all the responses! Ian Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253)

[AOLSERVER] connsperthread

Well, I tried uncommenting the connsperthread and setting it to 2 so I can have 2 connections to the database within a thread. However, it does not seem to work. It looks like this... ns_param connsperthread 5 ;# Normally there's one conn per thread But I get this...