Great news, and thanks to you and your team, Gustaf for this tremendous work.
Brian
From: Gustaf Neumann
Sent: Wednesday 2 March 2022 09:23
To: Navidevel
Subject: [naviserver-devel] Fwd: NaviServer Wins an Award from SourceForge
This message's attach
Dear all,
NaviServer has just been recognized with the Community Choice award by
SourceForge, which - to my understanding - reflects in essence the
number of downloads from sourceforge. As an official winner of the
Community Choice Award, we have the permission to use the award badge
wherever
Thank you!!! very much!
On Tue, Apr 17, 2018 at 3:05 PM Gustaf Neumann wrote:
> ns_share is outdated since ages. the workaround in [2] is not fixinig
> ns_share, but replacing ns_share via nsv commands. Have you looked at [1]?
>
> -gn
> PS: i've fixed just now the nsshare module on bitbucket to
ns_share is outdated since ages. the workaround in [2] is not fixinig
ns_share, but replacing ns_share via nsv commands. Have you looked at [1]?
-gn
PS: i've fixed just now the nsshare module on bitbucket to make it
compile with actual compilers, against actual version of Tcl and
NaviServer. .
I'm doing some work for a customer of mine, and he is still running
aolserver 3!!!
It is 15 years system running on fedora server! really old one with
postgres 8.
In my test I have manage to move the server to work with postgres 9.6 and
aolserver 4.5, but I still on the process for moving it to ru
On 02.10.2007, at 22:12, Stephen Deasey wrote:
> Some one who uses the chan stuff should fix up those tests and add
> some more to exercise ns_chan.
i.e. myself... OK, got the message...
Although when I start to test it I will most definitely
want to change that [ns_chan] syntax because I dislik
On 02.10.2007, at 22:05, Stephen Deasey wrote:
>
> You missed 'status', hidden among all those ? ? ? ? ? ? :-)
I know I know... I just wanted to check the complete
syntax w/o looking at the manpage ;-)
-
This SF.net emai
On 10/2/07, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote:
> hi Stephen,
>
> Begin forwarded message:
>
> > ! connPtr->responseLength = -1; /* -1 == unknown (stream), 0
> > == zero bytes. */
>
>
> Allright. "-binary" option to ns_headers, no optional length arg.
> I can live with that.
The two
On 10/2/07, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote:
>
> On 02.10.2007, at 21:48, Vasiljevic Zoran wrote:
>
> > hi Stephen,
> >
> > Begin forwarded message:
> >
> >> ! connPtr->responseLength = -1; /* -1 == unknown (stream), 0
> >> == zero bytes. */
> >
> >
> > Allright. "-binary" option to
On 02.10.2007, at 21:48, Vasiljevic Zoran wrote:
> hi Stephen,
>
> Begin forwarded message:
>
>> ! connPtr->responseLength = -1; /* -1 == unknown (stream), 0
>> == zero bytes. */
>
>
> Allright. "-binary" option to ns_headers, no optional length arg.
> I can live with that.
Ah,
lexxsrv:nsc
hi Stephen,
Begin forwarded message:
> ! connPtr->responseLength = -1; /* -1 == unknown (stream), 0
> == zero bytes. */
Allright. "-binary" option to ns_headers, no optional length arg.
I can live with that.
Apropos new tests that use thread extension and thread::transfer
command; this
11 matches
Mail list logo
