> Effectively, what I need is a upside-down of the > Tcl model: one interp any many threads. > Don't tell me: go shop Java. This does not compute > (for various unrelated reasons).
You can use ns_job, you define how may Tcl interp/threads you may use and then just submit tasks, each task will get state and do the work. I guess you already explored that. >> and, do why do you need all separate 1000 threads for every user, is >> the >> requirement to be connected to all at the same time? just wondering > > Yes. 1000's of workstations may be connected all the time > and over a long time. And all of them are pumping data to > the server, mostly. Doing this in a event-loop mode is > possible but not feasible. I must isolate everybody in a > thread because of the potential (complex) state that each > connection may have. You may combine methods, like let one thread to handle several connections sequentially if that will work but i do not have exact details so i will stop now. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
