Re: [naviserver-devel] Tcl inits

2007-08-07 Thread Zoran Vasiljevic
Am 06.08.2007 um 14:10 schrieb Gustaf Neumann: > however, concerning getting openacs to work on naviserver, > i would prefer having support for some time the good old blueprint > way. I understand. So the idea is to: a. keep the introspective loader b. design some "package loader" for A

Re: [naviserver-devel] Tcl inits

2007-08-07 Thread Zoran Vasiljevic
Am 06.08.2007 um 19:24 schrieb Stephen Deasey: > IIRC namespaced variables aren't touched because it would be too > expensive. > > Do they get cloned at startup though? This test: > > test init-1.4 {namespace variables do not get cloned} -body { > ns_job wait $qid [ns_job queue $qid { info

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Zoran Vasiljevic
Am 06.08.2007 um 19:24 schrieb Stephen Deasey: > On 8/6/07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: >> >> As of today, what we have is: >> >> a. >> introspective script based on the "old" way as 4.0 AS >> did it (init the interp by loading all Tcl files then >> run a script to pul

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Stephen Deasey
On 8/6/07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > > As of today, what we have is: > > a. > introspective script based on the "old" way as 4.0 AS > did it (init the interp by loading all Tcl files then > run a script to pull-out namespaces, variables etc "variables etc." -- do w

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Zoran Vasiljevic
Am 06.08.2007 um 18:54 schrieb Zoran Vasiljevic: > > I modified the "old way" NOT to use introspective > script, rather to use Tcl command traces :-) OK, not really *everything*. Tcl namespace serialization (variables/procedures) is still done "the old way". The problem with that that a namespa

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Stephen Deasey
On 8/6/07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > Hi! > > After spenging a weekend over this, I know less than > before... > > The question is how we are going to improve the Tcl > initialization so people could benefit from that better > than now? > > As of today, what we have is: > > a. >

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Zoran Vasiljevic
Am 06.08.2007 um 18:47 schrieb Vlad Seryakov: > I would keep old initialization if i need speed, if performance is > going > to suffer with Tcl/ns_ictl approach, then for fast/busy sites we > need to > be able to use old(fast) way. Otherwise, the server will be limited > for > non-realtime

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Vlad Seryakov
I would keep old initialization if i need speed, if performance is going to suffer with Tcl/ns_ictl approach, then for fast/busy sites we need to be able to use old(fast) way. Otherwise, the server will be limited for non-realtime or personal web sites usage only. Zoran Vasiljevic wrote: > Hi!

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Gustaf Neumann
Zoran Vasiljevic schrieb: > I think that old AS approach is the worst as it is really limited. > true. and not scalable > The Tcl-trace based approach is better but is known to have some > problems (I do not know which ones), yet, it is pretty powerful > and has some other nice side-effects (les

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Neophytos Demetriou
Hi Zoran, I've spend the weekend compiling and re-compiling the kernel and different versions of gcc/glib on two machines (with different CFLAGS/CHOST settings). NS "make test" worked only once on one of the two machines (with CHOST set to "i386-pc-linux-gnu" - GCC 4.2 no longer supports that). T

Re: [naviserver-devel] Tcl inits

2007-08-06 Thread Neophytos Demetriou
Hi Zoran, I've spend the weekend compiling and re-compiling the kernel and different versions of gcc/glib on two machines (with different CFLAGS/CHOST settings). NS "make test" worked only once on one of the two machines (with CHOST set to "i386-pc-linux-gnu" - GCC 4.2 no longer supports that). T