[AOLSERVER] Virtual hosting in 4.0b1
I just compiled 4.0b1 straight from CVS and it seems to be running but I can't get it to do virtual hosting, which, as I assume, it should do out-of-the box without the need to do nsvhr->nsunix/nssock. However, a naïve setup with one server master.mydomain.com running on port 80 and other second.mydomain.com on 8001 didn't work. Explicit second.mydomain.com:8001 works, but I was sort-of hoping that second.mydomain.com will work as well with master.mydomain.com getting the request and routing it appropriately. AFAIK it's not yet documented anywhere how it's supposed to work so maybe someone on the list will have an idea.
Re: [AOLSERVER] Virtual hosting in 4.0b1
To answer my own question: it works with nsvhr on port 80, redirecting "http:127.0.0.1:otherport" and other server running of course on 127.0.0.1:otherport. So I have virtual server in one process now. Life's good. > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Yon Derek > Sent: Sunday, June 10, 2001 11:47 PM > To: [EMAIL PROTECTED] > Subject: [AOLSERVER] Virtual hosting in 4.0b1 > > > I just compiled 4.0b1 straight from CVS and it seems to be > running but I can't get it to do virtual hosting, which, as I > assume, it should do out-of-the box without the need to do > nsvhr->nsunix/nssock. > > However, a naïve setup with one server master.mydomain.com > running on port 80 and other second.mydomain.com on 8001 > didn't work. Explicit second.mydomain.com:8001 works, but I > was sort-of hoping that second.mydomain.com will work as well > with master.mydomain.com getting the request and routing it > appropriately. AFAIK it's not yet documented anywhere how > it's supposed to work so maybe someone on the list will have an idea. >
Re: [AOLSERVER] several questions - mostly C API
In 4.0 name-base vhosting should just work. I got it working with current CVS code (nsvhr as a proxy on port 80 and other hosts bound to whatever port) so if your needs aren't bigger than that (name-based vhosting within one process) you shouldn't need any code changes. > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Wojciech Kocjan > Sent: Thursday, June 14, 2001 2:36 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] several questions - mostly C API > > > On Thu, 14 Jun 2001, Rob Mayoff wrote: > > > 1. Can I use Ns_TclGetConn(NULL) in a function which is set to > > > handle url2file? > > You can use that, or just Ns_GetConn. However, neither of > these will > > work in 4.0. > > Well, basically what I want is the url2file to return path > using the hostname from conn. Any chance of doing that in 4.0? > > > Use a TLS. Check out Ns_TlsAlloc, Ns_TlsGet, Ns_TlsSet. Look at > > dstring.c and serv.c for examples. > > Ns_Tls mytls; > in Module_Init: > Ns_TlsAlloc(&mytls,NULL); > > in my handler: > struct mystruct mys; > Ns_TlsSet(&mytls,&mys); > > and someplace in the xmlreturnfunc: > struct mystruct *ms; > ms=Ns_TlsGet(&mytls); > > That's basically it? > > -- > Wojtek Kocjan > [EMAIL PROTECTED] >
Re: [AOLSERVER] ns_xml module node count
I think this is mentioned in libxml faq ( http://www.xmlsoft.org/FAQ.html ), point 1 in Developer corner section. > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Tom Jackson > Sent: Thursday, June 14, 2001 3:03 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] ns_xml module node count > > > Rewriting the xml like below seems to remove the problem: > > >11 >21 > > > --Tom Jackson >
Re: [AOLSERVER] several questions - mostly C API
Could you share the libxslt interface code? Post it somewhere on the web, for example. Thanks, > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Wojciech Kocjan > Sent: Thursday, June 14, 2001 1:38 PM > To: [EMAIL PROTECTED] > Subject: [AOLSERVER] several questions - mostly C API > > > Hi there. > > I've been working on AOLserver for about a month and I got to like it. > > I wrote a small hack to allow name-based vhosting and now I'm > writing a module to do html=(xml+adp)+(xslt+adp). > > Here are my questions: > > 1. Can I use Ns_TclGetConn(NULL) in a function which is set > to handle url2file? - I did > Ns_SetUrlToFileProc(hServer,myProc) and myProc gets Ns_Conn > from Ns_TclGetConn(). Is that possible to do? I know that it > works on 3.4 for me... And no mistakes on heavy loads... (I > combined it with ns_mutex + nsv_* to check if it it's thread-safe :). > > 2. I'm using libxml2+libxslt and there's a function > xmlSetGenericErrorFunc(). I want my XML/XSLT parsing errors > to be printed out on output. > > I suppose I could create a hashtable+Ns_Mutex, create a > structure, connect it (by the hashtable) with Ns_Conn. But it > seems a bit inefficient to me... > > Any other way to store data connected with Ns_Conn. > > I probably want to store a DString and an int to check the > number of errors (mostly if any occured :) and print out the > errors using Ns_QuoteHtml()... > > Any ideas on how to write that? > > 3. Does anyone here (mostly from Poland I guess :-) knows > why/how www.onet.pl is using AOLserver? - AFAIR they're not > using Tcl at all... > > -- > Wojtek Kocjan > [EMAIL PROTECTED] >
[AOLSERVER] ANN: XSLT support in ns_xml available
I've added XSLT support to nsxml module. All information is available here: http://acs-misc.sourceforge.net/wiki/index.php?XsltSupportForAolserver I'll maintain nsxml module so if you have bugfixes, send them to me. Anyone in power here can give me CVS commit access to AOLServer@sourceforge (my user name is yond)? Or at least would one of those who have commit rights apply the patch? I can setup my own CVS but I would like to avoid nspostgres-like situation (people very confused about where to get nspostgres from).
[AOLSERVER] ANN: nsxml 1.2 released
Version 1.2 of nsxml module for OpenNSD/AOLServer has been released. All the gory details are here: http://acs-misc.sourceforge.net/nsxml.html Since this version has some major bugfixes (including one that can change the behaviour of scripts), I enourage everyone using it to upgrade and re-check their scripts. Release notes Version 1.2 has been release on 07/04/2001 and contains some major bug fixes, so everyone is encouraged to upgrade. Changes since previous release: * XSLT support has been added in the form of ns_xml apply_xslt $xslt_doc_id $xml_doc_id and ns_xml parse_xslt ?-persist? command. You need to install libxslt for it to work. * looks like ns_xml has not been updated to libxml2 which would result in the ns_xml doc root not returning a root but a node below the root. Most visibly, if there was a inside XML doc, you would only get a couple of nodes and not the whole doc. Fixed. May change behaviour of scripts. * ns_xml parse -persistent was broken (would crash) because a hash table for persistent docs has not been initialized. Fixed by initializing hash table. * ns_xml stats was broken, free() was used to free the memory allocated by ckalloc(). Fixed by calling ckfree(). * many commands didn't check for the number of arguments so they would crash if called incorrectly. Fixed by adding checks for a proper number of arguments. * fixed Windows compilation issues. * regression tests were written for the OpenNSD test framework. Tests cover all the issues above and then some.
[AOLSERVER] ANN: OpenNSD/AOLServer 4 beta 2
I've made a very unofficial realease of OpenNSD/AOLServer 4.0 beta 2. It's available here http://acs-misc.sourceforge.net/ns_rel_beta2.html The most interesting thing there are Windows binaries with nsxml, nsvhr modules and PostgreSQL database driver.
Re: [AOLSERVER] ANN: OpenNSD/AOLServer 4 beta 2
No, it isn't (that's why I said "unofficial" and I don't even mention AOLServer anywhere on the web page). I've added AOLServer so the folks on this list know that it's basically the same thing. However, the code is straight from AOLServer's CVS with a few bugfixes of mine. > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Titus Brown > Sent: Saturday, July 07, 2001 4:40 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] ANN: OpenNSD/AOLServer 4 beta 2 > > > On Sat, Jul 07, 2001 at 04:35:46PM -0700, Yon Derek wrote: > -> I've made a very unofficial realease of OpenNSD/AOLServer > 4.0 beta 2. > -> It's available here > http://acs-misc.sourceforge.net/ns_rel_beta2.html > > Hi, > > I > gather this isn't an AOLserver release, correct? The > "AOLserver" has me a bit confused... > > thanks, > --titus >
Re: [AOLSERVER] ANN: OpenNSD/AOLServer 4 beta 2
Well, for one OpenNSD/AOLServer confusion cannot be avoided, too late for that (in general). To clear things even more: this is not an "OpenNSD folks" release. This is "my little private release". Basically my goal was to give people Windows binaries for OpenNSD/AOLServer, nsxml, nsvhr and postgres driver to play with. The version number is 4 beta 2 because it's based on AOLSerer 4 beta 1 code, or at least that's how it's called in CVS. I've posted my fixes in bug tracker on sourceforge so I hope they'll end up in AOLServer tree as well. Some day. > -Original Message- > From: AOLserver Discussion > [mailto:[EMAIL PROTECTED]] On Behalf Of Titus Brown > Sent: Saturday, July 07, 2001 5:35 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] ANN: OpenNSD/AOLServer 4 beta 2 > > > -> No, it isn't (that's why I said "unofficial" and I don't > even mention > -> AOLServer anywhere on the web page). I've added AOLServer so the > -> folks on this list know that it's basically the same thing. > -> > -> However, the code is straight from AOLServer's CVS with a few > -> bugfixes of mine. > > Not to argue one way or the other about the split, but saying > "OpenNSD/AOLserver 4.0" -- that is, using a number that > *could* mean something in the AS releases, and moreover > preceding it with an "AOLserver" -- is not terribly clear ;). > > I'd really like to ask the OpenNSD people in general to make > this as clear as possible, because the split is going to > confuse a lot of people. By failing to indicate the > distinction between OpenNSD and AOLserver version numbers on > both the release Web page and in the e-mail, you've managed > to confuse me, at least. > > I suppose I should pop on over the OpenNSD bboards to ask > this, but I have a violently allergic reaction to those Web > bboards now, and it doesn't seem inappropriate for the > AOLserver list -- why did you decide to increment the major > version number? My understanding, perhaps flawed, was that > AOLserver is not moving to 4.0 for a while yet, and this > could cause a split in what major version numbers mean. > Since bug fixes usually don't cause a major version number > increment, I suspect that the "first" version of OpenNSD is > going to be 4, which has an even greater potential for confusion. > > I should say that I follow the AOLserver list only. Perhaps > I'm alone in my confusion, but I feel a looming sense of > dread that I've already been confused by the first "public" > announcement of the NSD folks... > > cheers, > --titus >
[AOLSERVER] ANN: Regression testing framework for OpenNSD/AOLServer
Some time ago there was some talk about testing AOLServer. You can find unofficially official release of nstest-0.1 (code-named "Unobtrusively Confusing"), regression testing framework for OpenNSD/AOLServer, here: http://acs-misc.sourceforge.net/nstest-manual.html Comments and suggestions (technical) welcomed.
Re: [AOLSERVER] Problems compiling AOLSrv 3.4 in Win2000 - (tcl8x.c missing in 3.4 distribution)
The short answer is that 3.4 has not been mainted wrt. to making it
compileable under windows so unless you're able to fix the code
yourself, you're out of luck.
If you feel brave, I've made binaries of AOLServer 4 beta (and some
other goodies) available here:
http://acs-misc.sourceforge.net/ns_rel_beta2.html. You can also download
the sources and they should compile out-of-the box on windows.
You have to be brave because this code is not stable, I'm fixing the
issues as I encounter them (e.g., I just found one bug today that I
haven't yet incorporated into this release).
> -Original Message-
> From: AOLserver Discussion
> [mailto:[EMAIL PROTECTED]] On Behalf Of Ariel E. Carná
> Sent: Wednesday, July 11, 2001 10:31 PM
> To: [EMAIL PROTECTED]
> Subject: [AOLSERVER] Problems compiling AOLSrv 3.4 in Win2000
> - (tcl8x.c missing in 3.4 distribution)
>
>
> Hi to everyone!
> I'm compiling AOLServer 3.4 on Win2000, after read a message
> from Kris Rehberg indicating that the file "tcl8x.c" was
> moved to "tcl8.3.2/generic/nsthreads.c" and in consequence is
> neccesary to change the win32 project to reflect this.
>
> Then I changed the project. I added the file "nsthreads.c" to
> the group files "nsthread" under the folder "Source files".
> After do it, when I try to compile all the project I get this error
> messages:
>
> ..\..\tcl8.3.2\generic\nsthreads.c(118) : warning C4273:
> 'Tcl_CreateThread'
> : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(222) : warning C4273:
> 'TclpThreadExit' : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(272) : warning C4273:
> 'Tcl_GetCurrentThread' : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(300) : warning C4273:
> 'TclpInitLock' : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(324) : warning C4273:
> 'TclpInitUnlock' : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(347) : warning C4273:
> 'TclpMasterLock' : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(371) : warning C4273:
> 'TclpMasterUnlock'
> : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(397) : warning C4273:
> 'Tcl_GetAllocMutex'
> : inconsistent dll linkage. dllexport assumed.
> ..\..\tcl8.3.2\generic\nsthreads.c(426) : error C2143: syntax
> error : missing '{' before '*'
> ..\..\tcl8.3.2\generic\nsthreads.c(427) : error C2449: found
> '{' at file scope (missing function header?)
> ..\..\tcl8.3.2\generic\nsthreads.c(429) : error C2059: syntax
> error : '}'
> ..\..\tcl8.3.2\generic\nsthreads.c(452) : error C2449: found
> '{' at file scope (missing function header?)
> ..\..\tcl8.3.2\generic\nsthreads.c(454) : error C2059: syntax
> error : '}'
> ..\..\tcl8.3.2\generic\nsthreads.c(479) : error C2449: found
> '{' at file scope (missing function header?) ... ... ... I
> have compiled the others previous version of AOLServer
> without problems but now...I need a little help of my
> friends! :-)
>
> What's are exactly the changes necessaries to do on Win32?
>
> Thank to everyone.
>
> Ariel.
>
Re: [AOLSERVER] perms
> Certainly... what I am working on is as close to live > updating as possible of users for a subscription based > website.. we are using a third party to charge cards and > generate the accounts for us, so I have to work around that > difficulty.. I'm interested in the on-line billing options. Would you care to share who's doing the credit card charing and your experiences so far? I would appreciate any real-life info. Regards,
Re: [AOLSERVER] correction! sorry
What is the difference between: ns_param map "GET /cgi /usr/local/cgi" (the first sample config on your page) And ns_param map "GET /*.cgi /" (second sample config). I mean the difference between "GET /cgi" and "GET /*.cgi"? What scripts will be matched for "GET /cgi"? Also this page is not linked from main scottg.net, is this intentional? Thanks for a very nice article. > -Original Message- > Ok, I've added this info to the docs at: > > http://scottg.net/webtools/opennsd/modules/nscgi
Re: [AOLSERVER] Resume download for AOLServer
> > > is there a way to resume download for AOLServer? > > > > What do you mean? Do you mean that you want a program like > GetRight > > or wget to be able to resume a download FROM an instance of > AOLserver? > > > > If so, you can try 3.2+ad12 or 3.3+ad13. I implemented support for > > byte ranges (which is how download resumption works) in those > > versions. AOL hasn't adopted that patch yet (AFAIK). > > I hope they dont unless they give an option to disable it... > I don't want my webservers to get hammered with file downloads That is assuming that some random X on the internet will decide to hammer you with downloads based on the presence (or lack of it) of download resumption in your web server. I don't think this is a valid assumption. If anything, you're worse off without download resumption because in case of connection drop you'll get hammered again, but starting from the beginning.
Re: [AOLSERVER] installing AOL Server on WINDOWS!
> Also do you have an URL for a nsvhr setup doc? I don't know > where to begin on that. But it's a make-or-break issue for > us, and a lot of other companies I'm sure. Any experience I > get from doing it on Windows will be contrib'd back to the group. To the best of my knowledge nsvhr as present in AOLServer CVS tree doesn't even compile under windows so unless you can fix it (which is not hard) you won't get it. The only known (to me) place you can get nsvhr under windows is in my own private "fork" of AOLServer 4 beta available here: http://acs-misc.sourceforge.net/ns_rel_beta2.html It also has nsxml, nspostgres, nscache and nssha1. Don't use it for production work. You've been warned.
Re: [AOLSERVER] installing AOL Server on WINDOWS!
> Tell you what, I can walk you through that if you'll walk me > through the same thing with PostGreSQL. I just did AOLserver > last week, from the binaries, not the C source. If you need > to compile it from the source I can't help you. I have battle-tested info on installing PostgresSQL on Windows here: http://acs-misc.sourceforge.net/acs3xwin.html (part of it). If you try it and it doesn't work, tell me about (although I did at least 2 installs from scratch following my own instructions). The only thing is that if you want to access it from AOLServer on Windows, you need to have nspostgres module and supporting *dll which, to the best of my knowledge, aren't available in a nice package except for this place: http://acs-misc.sourceforge.net/ns_rel_beta2.html
Re: [AOLSERVER] Nonblocking calls and EWOULDBLOCK
Beware: take this with a BIG grain of salt. After an hour of staring at TCP implementation in kernels 2.2.18 (~RH 6.2) and 2.4.4 (~RH7) (i.e. tcp_recvmsg() in \linux\net\ipv4\tcp.c it looks like it's exactly how they work. In 2.2.18 if len = 0 it will return 0/no error and there is a enlightning comment near that code: /* * BUG BUG BUG * This violates 1003.1g compliance. We must wait for * data to exist even if we read none! */ In 2.4.4 it will try to read the data anyway and if there is no data and socket is NOBLOCK (timeo==0) it'll return EAGAIN=EWOULDBLOCK. So presumably that was a bug in 2.2.x fixed in 2.4.x. But again, I wouldn't trust my analysis, after all I'm not really sure if it even goes through this codepath. I would only trust stepping through the code in the debugger but given that I won't do it, eyeballing the code is second best alternative. You can check it out for yourself, it's fun. > I am experiencing a difference in behavior in nsunix between > Red Hat 6.1 (kernel 2.2.14) and Red Hat 7.1. I don't have > 7.1 to develop on, this is basically, a user report > > In 6.1, when I call recvfrom within nsunix.c/GetDATAFromUDS, > it returns 0, as in 0 bytes were available. > > The exact same call from 7.1 returns a -1, and an errno of > EWOULDBLOCK. > > struct sockaddr_in sa; > intsize; > size = sizeof(sa); > > . . . > > nbytes = recvfrom(sock,NULL,0,MSG_PEEK,&sa,&size); > > In both cases, the underlying socket has been tagged as > nonblocking, and in fact, I can basically expect that there > is nothing to read from the socket for most GETs. That's > okay. As you can see, the call to recvfrom asks for 0 bytes, > and is called for its side effect: to fill out the > sockaddr_in structure which yields the IP address of the > client browser. > > I can understand the 6.1 behavior of recvfrom: I was asked > for 0 bytes, and > 0 bytes were available, so return 0 bytes. I can rationalize the 7.1 > behavior. There are no bytes in the buffer, so I will have > to issue a read to read any bytes that I have to return. > Since I am nonblocking, return -1 and an errno of EWOULDBLOCK. > > So my question is: does anyone actually know what's going on? > Is there a kernel bug here in either 6.1 or 7.1? Should a > nonblocking call be able to return 0 bytes?
Re: [AOLSERVER] Nonblocking calls and EWOULDBLOCK
> how did you know where to look, > what tools do you use to navigate the lower levels of linux, > and can you recommend a "gentle" introduction to lower levels > within the kernel? Tools: I used little known but the best programmer's editor I know: SourceInsight (http://www.sourceinsight.com/). It might not be kosher for some (windows only) but it's just awesome. It's highly oriented towards C/C++/Java but for coding in those languages it's simply the best. The biggest thing about SI is its ability to parse C/C++ code so it knows which string is a variable, class member, enum etc. (and it's not a primitive regexp parsing as in Emacs or most other tools good only for syntax highligting, I believe they have pretty much full C/C++ parser). SI really shines when you have to navigate through big programs (especially the code you don't know). This is something I tend to do a lot and I can't imagine doing that without SI. They have a trial version, play with it. I belong to those 42% (http://www.sourceinsight.com/eval.htm) that say that SI "Greatly improved productivity". Highly recommend. How did I know: I created a SourceInsight project for each kernel, SI parsed and indexed all files in a few minutes, I looked for places where EWOULDBLOCK is used in the whole tree, not many of them but noticed that EAGAIN is a synonim, so looked for EAGAIN, used in many places. I figured out that the function would be called somewhat *recv*, I spent some time in af_unix.c and af_inet.c but that wasn't it, found tcp.c, read it for a while and decided that that's it. In other words: guess work that wouldn't be possible (or at least not so easy) without SI. Introduction: I don't know, this is the first time I've read kernel source and I haven't read any intros. There are some books about kernel, both on the net and on paper. But if you want just to answer a very specific question (as in this EWOULDBLOCK example) SourceInsight + sources are your best bet.
Re: [AOLSERVER] Nonblocking calls and EWOULDBLOCK
I know. There is also Source-Navigator from Cygnus/RedHat (http://sources.redhat.com/sourcenav/). I haven't played with cscopy (only looked at it some time ago), I did play some with SourceNavigator. I just think that SourceInsight people got this thing right. I almost enjoy using it (which is quite a feat since I'm mostly frustrated that software doesn't do what I would like it to do the way I think it should be done). > The cscope program runs on Unix and provides a lot of what > you describe in SourceInsight. Emacs, vim, and nvi have > integrated support for cscope. > > http://cscope.sourceforge.net/
Re: [AOLSERVER] AOLserver at SourceForge, Modules and some suggestions
There are two reasons. 1. Distributed development has its merits, mainly, you don't have to coordinate. It also has the drawback you noticed: it allows lack of coordination. 2. Historically AOLServer team and keepers of SF project have been absolutely unacommodating to the needs of what we like to call "community". It shows by bugs lingering in the bug database for ages, major changes (like the recent one to drop win support) being done without an announcement (not to mention prior discussion). If you read it as a critique or rant - don't. It's a fact. They have the right to do whatever they please but that's the consequence. I for one wouldn't start acs-misc if I could just get my fixes to ns_xml into AOLServer project without a hassle. That would be the best solution. Since that's not the case (esp. the "hassle" part) I've chosen second best solution: put it into a separate CVS where I have full control, knowing perfectly well that this will create a confusion (and not liking that). As to your proposition - it's a great idea albeit slightly unrealistic esp. trying to get people to write regression tests (IMHO, that is). > -Original Message- > From: AOLserver Discussion > > Where is the latest ns* module? Why do I have to manually > edit a module's Makefile? Why are these modules scattered all > of the net? How come we have the same module in multiple > places? Why does the coding style in one module look > completely different than the coding style for another > module? Why do neither of those conform to the style that the > AOLserver core uses? > > Right now, nssoap is a separate project; there are two > nsxml's on sourceforge, one in the AOLserver area, and one in > the acs-misc area. There's an nsgraph module on it's own. > nspostgres is in both AOLserver at sourceforge and is at the > OpenACS site (my fault: I asked for it to be imported into > AOLserver@SF so I could apply the standard AOLserver C coding > styles and maintain it). And more. > > Many of the modules I've worked with compile differently. > nstomcat, for example, makes you copy the sources from it > into the Tomcat source tree, and then run make. Other modules > require you to hand-edit their Makefiles to get them to work > instead of passing params on the command line to make. > > === > > The world seems to be going Java, but I, apparently, am a > neanderthal. I prefer C, Tcl, AOLserver. However, I need the > ability to do XML/XSLT to PDF, HTML and other formats, > *easily*, without having to re-engineer the modules I want to > use to get the job done, or write them from scratch. I simply > don't have the time, and I am *certainly* no coding genius, > nor do I plan to spend much of my spare time staring into the > phosphor. > > Looking around the net recently, I've seen a lot of Java > projects that attempt to do what I'm looking for. These > include Cocoon, WebMacro, the ACS, and Enhydra, to name just > a few. Most of these projects seem aimed to solve the problem > of handling the heavy work of web publishing/collaboration > while letting you focus on your apps at a high level. > > I like the idea of being able to plug in a .jar file and have > instant access to a tool I need, such as an XML parser, and > it looks like I'll be going the all-Java route in the near-future. > > === > > So, I need to be able to grab a new module, compile, install > and configure it and just have it *work*, without a lot of > monkeying around. And when I do need to monkey around with a > module, I would like it to follow a standard coding style so > I can easily work with it. > > Here are my suggestions: > > * Move all ns* modules into the AOLserver sourceforge area. > (Yes, *ALL* of them). > * Add the people who work on these modules to the AOLserver > committer's list > * Apply the standard build procedures to each module > * Apply the standard C coding style to each module > * Build regression tests for each module (a *must*) > * Write basic docs that cover a module's compilation, config and use > > > I can contribute my time to applying the standard build > procedures and reformatting/refactoring the code to conform > to the AOLserver coding style. Some discussion needs to be > done with regard to regression testing, and a template doc > needs to be generated. > > With a consistent, well-tested codebase, using or fixing > AOLserver modules should become significantly easier. And > it's not that much more work doing it right the first time. > > Is anyone interested?
