Forum OpenACS Development: Re: Is it time for NaviServ Again?
As for going in different direction than AS, that is true, we ported some stuff from AS 4.5 like new adp parser, pools, Tcl initialization but adjusting to our vision. Overall i think it is much better server than AS 4./4.5, it has support for many many features, a lot of modules and integrated many commands so no need for extra modules like nscache, nsha1, upload statistics for huge uploads, writers support for delivering huge files without using conn threads, embedded virtual hosting, no need for config or server restart to add new virtual hosts.
Also, docs are mostly up-to-date, for quick overview see:
Sorry for advertising, i did not post here for a long time.
Thanks for posting. My concerns were not intended to cause a switch to NaviServer, I don't know anything about it. I am interested in the seriousness of the developers, and AOLserver stock just went way down for me. Is it possible for you to describe here what is NaviServer? I will follow your link, but what is the diff with AOLserver and why did OACS need to be ported to NaviServer? Sorry, but porting sounds like a major process.
Naviserver is fork of AS 4.0.11 but this year we ported some stuff from AS 4.5, mostly pools, tasks, new ns_http command but NS has new ns_https/lightweight nsssl module.
As for seriousness, Zoran relies its business on it, i am using it as swiss knife and actually at my new company we are using it for backend/server parts, i am not sure how Stephen relies on it. And, this is opensource project, we do not have many commiters but this is because of lack of popularity, we never intended to fight for aolserver developers or lure them from AS.
concerning "no porting is needed": well, naviserver 4.99.1 did not work out of the box with openacs due to interface changes between aolserver and naviserver. See for a summary, what was necessary for getting naviserver 4.99.1 to work with openacs:
see for example these two changes.
Also openacs-4.5 required a few changes in openacs when it came out.
With the various head versions of naviserver, i had in the past problems with the loading semantics, ns_cache and encodings. All of these problems are fixable to work with minimal invasive changes with openacs, but i don't expect the naviserver head version to work out of the box right now.
Concerning seriousness: i have no doubts about seriousness of the naviserver team, naviserver is here to stay.
Vlad, is there a reason that the nice documentation is your site and not on the naviserver sourceforge site?
We've decided to minimize maintenance efforts still to use SF and CVS but i am personally do like it but this is in no way some kind of fork or anything pulling from the project, just faster access.