Thank you
Regards,
Sassy Natan
972-(0)54-2203702
On Wed, 27 Nov 2024 at 10:00 Gustaf Neumann (sslmail)
wrote:
> Progress report from the documentation cleanup;
>
> > 4) the parameters of the implemented commands should be documented and
> vice versa.
>
> Some first numbers, worse than expec
Progress report from the documentation cleanup;
> 4) the parameters of the implemented commands should be documented and vice
> versa.
Some first numbers, worse than expected:
From the currently 464 documented commands, the arguments in the source code
differ in more than 50 % of the cases
-
:19 am
To: naviserver-devel@lists.sourceforge.net
Subject: Re: [naviserver-devel] ns_set reform
Dear all,
>From the previously state goals:
> 1) all commands tested in the regression test should be documented
> 2) all documented commands should be tested (at least syntax-tested)
&
Thank you.
This project is so impressive and was really introduced things head off its
time.
I’m working with Navi since 2002 when node js, python and all other new
programming languages was never adapted the method of being the web server
embedded in the language itself.
AOL or Navi was from day
Hello, thank you for hard work. And I think nobody using this commands any
more.
On Fri, 22 Nov 2024, 09:20 Gustaf Neumann (sslmail),
wrote:
> Dear all,
>
> From the previously state goals:
>
> > 1) all commands tested in the regression test should be documented
> > 2) all documented command
Dear all,
From the previously state goals:
> 1) all commands tested in the regression test should be documented
> 2) all documented commands should be tested (at least syntax-tested)
> 3) all implemented commands should be tested
> 4) the parameters of the implemented commands should be d
> However, based on a quick grep, there are still several hundred syntax tests
> missing.
Some more precise data: We have in NaviServer altogether 638 (!) documented
commands including subcommands,
Especially there are still many subcommands, which are not syntax tested.
Yesterday and today
Dear all,
i’ve implemented the changes with case-insensitive ns_sets, and they are
working nicely. These changes are highly backwards compatible, no changes were
e.g. necessary for OpenACS.
The new version is still verbose, when e.g. a “get” or “update” operation
happens on a case-insensitive
f Neumann (sslmail)
Sent: Thursday 7 November 2024 10:13 am
To: naviserver-devel@lists.sourceforge.net
Subject: [naviserver-devel] ns_set reform
Dear all,
The upcoming release of NaviServer 5 includes several enhancements to "ns_set",
such as more efficient storage management and the additio
Dear all,
The upcoming release of NaviServer 5 includes several enhancements to "ns_set",
such as more efficient storage management and the addition of the "-all" option
for "ns_set get" and "ns_set iget". I also plan to implement further
improvements.
One common problem area is the handling o
Dear all,
over the last days, I've worked on improving scalability of ns_set
operations in NaviServer, which are used on multiple crucial places such as:
- ndsb interface (returning tuples as ns_sets)
- configuration values
- headers
The classical implementation for ns_sets uses separately
11 matches
Mail list logo
