On Tuesday 08 March 2005 15:30, Vlad Seryakov wrote:
> i have bash alias ncp="socat readline tcp4:localhost:2080" and then i
> can type/execute anything
Ah... GPL! I knew there is a catch! My first impression was:
DAMN! So many development for nothing!
(after I saw that this thingy would s
> Then nscgi - usefull, nsco - usefull, nsperm - ???, nsext - ???
seems there is a constant interest in nscgi, at least it was talked about a
lot of times in the aol-mailinglist.
> Not much to have working server, some DB modules should be there, at
> least PG, MySQL, SQLite,
> thi is the main s
New driver looks interesting but nothing major different from 4.0 except
limit pools, and the
driver code/logic looks even more complex. Connection and Sock
separation is good but still
except dynamic limits i do not see advantages of the new driver, of
course it is not finished yet but i heard
I think it would be very difficult to come up with a standard set of
these higher-level features that would please everyone. I'd like to
see lot of extra modules in cvs though.
Yes, in CVS, packaging is another issue but having module sin CVS and be
able to download them from one
place is w
I am using ncp module with socat which supports readline:
i have bash alias ncp="socat readline tcp4:localhost:2080" and then i
can type/execute anything
there. Never thought about anything else since. The only thing that
needs to be tested with browser
is connection stuff, like cookies/heade
On Tuesday 08 March 2005 09:09, Stephen Deasey wrote:
> I'm not sure what the right way to go here is. Would such an nsdsh be
> useful, or should we just add more to the server binary, or should I
> just be a bit more creative when writing tests..?
>
I do not know if this is what you'd need...
On Tuesday 08 March 2005 06:02, Stephen Deasey wrote:
> 2005-03-08 06:02
>
> I don't think you need this. In 4.x all content is read fromt the
> network and buffered before your code ever runs. You're just copying
> it from one buffer to another.
OK. I did not know that. This command is still
Neither RedHat or Fedora ship with a threaded build of Tcl, so I build
my own package and install in parallel with the original. I've been
naming the tclsh84 executable nsdsh.
Our tests, such as they are, also need to run in a threaded Tcl shell.
Which one? How to find it? Maybe we should build
