Danil:
In real-time or high performance applications, the very act of loading
the code into a debugger is going to affect, or perhaps completely
distort, the performance of the program and quite possibly alter or
mask the very problems you are trying to fix. A well-placed print
statement
On 07.09.2006, at 16:36, Rusty Brooks wrote:
I'd like to see this as a feature of AOLServer... being able to
mark a channel as do-not-cleanup.
You can open a (tcl) channel in one thread, then detach it from the
interpreter/thread and re-use (i.e. attach) it into some other thread.
The only
John,
I tried to do this once, for similar reasons. When a connection closes, all
open files are closed. I'm not sure of any better way to run the server: if
you don't have automatic code closing open files, then you run the risk of an
error leaving your file open, and then you might screw up
On 2006.09.07, Rusty Brooks [EMAIL PROTECTED] wrote:
I'd like to see this as a feature of AOLServer... being able to mark a
channel as do-not-cleanup.
I honestly don't think this is what you really want.
Please look at [ns_chan] --
http://panoptic.com/wiki/aolserver/Ns_chan
-- Dossy
--
Guys,
I have a similar issue with redirects crashing the nsd 4.5.0, and I got a
quickie fix to prevent the crash.
Please check out this thread
http://openacs.org/forums/message-view?message_id=471882
Of course, this does not fix the root cause (and apparently produces zombies),
but at least it
On 2006.09.07, Rusty Brooks [EMAIL PROTECTED] wrote:
I think it probably is. Why don't you think so? My goal is to open one
channel per thread and not have it close, until I tell it to.
Can any request from any user use any previously opened channel? i.e.,
is the channel's use stateless?
On 2006.09.07, Alex Andryushkin [EMAIL PROTECTED] wrote:
I have a similar issue with redirects crashing the nsd 4.5.0, and I got a
quickie fix to prevent the crash.
Please check out this thread
http://openacs.org/forums/message-view?message_id=471882
Of course, this does not fix the root
Instead of trying to give additional advice on this subject, I'll just make an
observation: most of us are here to discuss how to use AOLserver, not how to
introduce more bugs.
tom jackson
On Thursday 07 September 2006 08:13, Rusty Brooks wrote:
Dossy Shiobara wrote:
On 2006.09.07, Rusty
It's stateless. Think of it like a database connection. AOLServer just
needs to pipe commands to this channel and get results back.
Rusty
Dossy Shiobara wrote:
On 2006.09.07, Rusty Brooks [EMAIL PROTECTED] wrote:
I think it probably is. Why don't you think so? My goal is to open one
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
Thankfully, it's open source, and I can introduce more bugs to my hearts
content!
Rusty
Tom Jackson wrote:
Instead of trying to give additional advice on this subject, I'll just make an
observation: most of us are here to discuss how to use AOLserver, not how to
introduce more bugs.
tom
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
On 2006.09.07, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
On 9/7/06, Dossy Shiobara [EMAIL PROTECTED] wrote:
Can you try CVS HEAD ... see if it fixes the crash bug properly?
Done and fixed. Thank you :)
Phew! I guess it's time to start thinking about a 4.5.1 release ...
-- Dossy
--
On 9/7/06, Dossy Shiobara [EMAIL PROTECTED] wrote:
Can you try CVS HEAD ... see if it fixes the crash bug properly?
Done and fixed. Thank you :)
Daniel
--
| ---
| Daniel P. Stasinski | http://www.saidsimple.com
| [EMAIL
14 matches
Mail list logo
