OK, I gave it a shot. I'm still going to look at the ns_chan info but
for now this will work. I'm trying to cobble together a
proof-of-concept to switch parts of our product from tclhttpd to
aolserver, and so I need something that works, this week, no matter what.
I would not implement it in aolserver core how I did it, which was to
nsv_lappend to a variable any channels that I wish to not have cleaned up.
My ns_cleanup chan lsearches that list before closing a channel, and if
the chan it's considering closing is in the list, it just skips it,
like it does for stdout etc.
Dossy Shiobara wrote:
On 2006.09.07, Rusty Brooks <[EMAIL PROTECTED]> wrote:
It's stateless. Think of it like a database connection. AOLServer just
needs to pipe commands to this channel and get results back.
Then, I'd try the suggestion of replacing ns_cleanupchans with your own
version that doesn't auto-close channels you want to preserve.
How to best implement that in general in the core AOLserver code will
benefit from any feedback you give based on your implementation and
experiences.
Let us know if/how it works for you,
-- Dossy
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
