Re: [naviserver-devel] The larch

2006-07-14 Thread Gustaf Neumann
Bernd Eidenschink schrieb: Hi friends, "and now to something completely different: the larch"... ;-) Some of you might know: http://www.zdziarski.com/projects/mod_evasive/ i have implented something similar (xotcl-request monitor) which you can get from the oacs cvs (still, xotcl style li

[naviserver-devel] The larch

2006-07-14 Thread Bernd Eidenschink
Hi friends, "and now to something completely different: the larch"... ;-) Some of you might know: http://www.zdziarski.com/projects/mod_evasive/ I'm just interested in some theoretical thoughts, if there would be a ns_evasive module... how to set up the "storage": Background (Remember: this i

Re: [naviserver-devel] SF CVS broken

2006-07-14 Thread Zoran Vasiljevic
Am 14.07.2006 um 16:15 schrieb Vlad Seryakov: PS: As you see SF issues come back every month with something different, usually resulted in no access. Yes, yes... I can read the hidden message... Zoran

Re: [naviserver-devel] running callbacks

2006-07-14 Thread Zoran Vasiljevic
Am 14.07.2006 um 16:13 schrieb Vlad Seryakov: I still think that you could build ns_callback command that will be similar to ns_conn, i.e. it works only in the context of callback like ns_conn in the connection thread only. This way you can extend it as you wish and be backward compatible

Re: [naviserver-devel] SF CVS broken

2006-07-14 Thread Vlad Seryakov
Same here, i submited bug to them but i see a lot of such submisions already, so it affected many people. PS: As you see SF issues come back every month with something different, usually resulted in no access. Zoran Vasiljevic wrote: Hi! Aparently, some accounts cannot login to CVS as they

Re: [naviserver-devel] running callbacks

2006-07-14 Thread Vlad Seryakov
I still think that you could build ns_callback command that will be similar to ns_conn, i.e. it works only in the context of callback like ns_conn in the connection thread only. This way you can extend it as you wish and be backward compatible Zoran Vasiljevic wrote: Am 13.07.2006 um 22:16 sc

Re: [naviserver-devel] Cache compiled Tcl page bytecode

2006-07-14 Thread Zoran Vasiljevic
Am 14.07.2006 um 16:04 schrieb Vlad Seryakov: In the nstk module i have generic caching of compiled pages and file.tcl can be modified to perform per-thread .tcl caching of bytecode as well. Yes, this is a trivial, poor-man's cache which is simple and works. Cheers, Zoran

Re: [naviserver-devel] Cache compiled Tcl page bytecode

2006-07-14 Thread Vlad Seryakov
In the nstk module i have generic caching of compiled pages and file.tcl can be modified to perform per-thread .tcl caching of bytecode as well. proc ns_sourcefile { path } { set proc0 [info procs filecache_$path] set cookie0 $stat(mtime):$stat(ctime):$stat(ino):$stat(dev) # Verify

[naviserver-devel] SF CVS broken

2006-07-14 Thread Zoran Vasiljevic
Hi! Aparently, some accounts cannot login to CVS as they get their password rejected. Same for me as of today. I do not know how long it will take now... Cheers Zoran

Re: [naviserver-devel] running callbacks

2006-07-14 Thread Zoran Vasiljevic
Am 13.07.2006 um 22:16 schrieb Stephen Deasey: Why can't you initialise resources when you register the callback? I don't think I understand the problem here... Well, my first idea was to get a kind of "self-initializing" and "self-cleaning" procedures. Most importantly the "self-cleaning"

Re: [naviserver-devel] running callbacks

2006-07-14 Thread Zoran Vasiljevic
Am 13.07.2006 um 22:16 schrieb Stephen Deasey: Ns_TclCallbackArgProc is only for reporting purposes, so it doesn't much matter. There should be lots of tests for this in the test suite Well, I see... for reporting this really does not matter. The output of this command can't be used for anyth

Re: [naviserver-devel] Cache compiled Tcl page bytecode

2006-07-14 Thread Zoran Vasiljevic
Am 13.07.2006 um 23:40 schrieb Stephen Deasey: I was suggesting that maybe there should be a away around this as in some cases, like ours, we specifically make sure that all interps are identical: we create one master interp at start up and then clone it for each new thread. No one seemed exc