On Sun, 06 Mar 2005 18:17:06 -0500, Vlad Seryakov
<[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> Do you have any roadmap-kind of plans or thoughts about naviserver?
> Slowly it is getting to the point when it can replace all my patched
> aolservers, i already use it at home instead of AS. As i remember
Sounds like a packaging problem to me. Bundling modules into the core
will only turn it into a development/release problem.
Large projects actually seem to be going the other way: Postgres are
moving things out of core and onto gborg; X.org is busy splitting up
into server, fonts, utils, etc.
It looks like the change was added to cvs-HEAD ~6 weeks ago, so this
probably wont find it's way to 4.0.10 at all...
I was just thinking we should keep parity with AOLserver here. The
new driver code promised for AOLserver might depend upon it and it
might start to get messy when we merge with 4.
Done except naming, it is different in AS 4.1 CVS and 4.0.x, does it
really matter much? But i am not insisting.
Stephen Deasey wrote:
How about removing the comment, marking the function void, and
changing the naming to match the addtions to AOLserver?
On Mon, 07 Mar 2005 23:53:35 -0500, Vla
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.
On Sat, 5 Mar 2005 10:38:09 +0100, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> > What is [ns_conn discardcontent] used for?
>
How about removing the comment, marking the function void, and
changing the naming to match the addtions to AOLserver?
On Mon, 07 Mar 2005 23:53:35 -0500, Vlad Seryakov
<[EMAIL PROTECTED]> wrote:
> Oops, i was thinking to retern previous status but then change my mind,
> comment left, i will corr
Oops, i was thinking to retern previous status but then change my mind,
comment left, i will correct it.
Stephen Deasey wrote:
The comment for Ns_ConnSetResponseStatus() says that it reurns the
previous status. It actually returns the current, just-set status.
So does ns_conn status.
I don'
The comment for Ns_ConnSetResponseStatus() says that it reurns the
previous status. It actually returns the current, just-set status.
So does ns_conn status.
I don't think it's neccessary. The other simillar functions in that
file have no return value. (Ns_ConnSetUrlEncoding(),
Ns_ConnSetWriteE
http://cvs.sourceforge.net/viewcvs.py/naviserver/naviserver/nslog/nslog.c?rev=1.3&view=log
The cvs commit message for nslog/nslog.c now reads:
"Add Ns_ConnSetResponseStatus command to be able to se response status
without touching headers. Also ns_conn status has been extended with
ability to se
- using -b 0.0.0.0 will listen on all interfaces
I'm afraid this is still not clear to me, but I'll have
to give you some examples why this is making me trouble.
I will prepare the switch to naviserver in our development
branch in couple of days and then this will be clear
More correct sol
On Monday 07 March 2005 17:19, Vlad Seryakov wrote:
> - using -b 0.0.0.0 will listen on all interfaces
I'm afraid this is still not clear to me, but I'll have
to give you some examples why this is making me trouble.
I will prepare the switch to naviserver in our development
branch in couple of day
- using -b 0.0.0.0 will listen on all interfaces
- watchdog has green light for commit
- there are always other tiny things :-)))
Zoran Vasiljevic wrote:
On Monday 07 March 2005 15:55, Vlad Seryakov wrote:
I don't, yet. My primary goal is to get to a point where we can
switch to naviserver in
On Monday 07 March 2005 15:55, Vlad Seryakov wrote:
>
> >
> > I don't, yet. My primary goal is to get to a point where we can
> > switch to naviserver internally. I'm still not there, so for me
> > there is more work to do.
>
> Can you tell what do you still need?
On the top of my head:
o. b
Yes, contrib directory is a good idea
Bernd Eidenschink wrote:
Hi Vlad,
I have no idea. We are using the server with our own templating
framework based on tDOM but I do not think this is something
of general interest.
I have light-weight templating i can extract and put into modules/tcl,
th
Hi Vlad,
> > I have no idea. We are using the server with our own templating
> > framework based on tDOM but I do not think this is something
> > of general interest.
>
> I have light-weight templating i can extract and put into modules/tcl,
> that will be one small file and will support OACS-styl
I don't, yet. My primary goal is to get to a point where we can
switch to naviserver internally. I'm still not there, so for me
there is more work to do.
Can you tell what do you still need?
I have no idea. We are using the server with our own templating
framework based on tDOM but I do not
Ouch, my bad
Zoran Vasiljevic wrote:
In nslog.c:
/* Get parameters from configuration file */
logPtr->rollfmt = Ns_ConfigGetValue(path,"rollfmt");
if (logPtr->rollfmt == NULL) {
logPtr->rollfmt = ns_strdup(logPtr->rollfmt);
}
This is not what the writer wanted, or?
I a
In nslog.c:
/* Get parameters from configuration file */
logPtr->rollfmt = Ns_ConfigGetValue(path,"rollfmt");
if (logPtr->rollfmt == NULL) {
logPtr->rollfmt = ns_strdup(logPtr->rollfmt);
}
This is not what the writer wanted, or?
I assume it should have been written as:
On Monday 07 March 2005 00:17, Vlad Seryakov wrote:
> Hi guys,
>
> Do you have any roadmap-kind of plans or thoughts about naviserver?
I don't, yet. My primary goal is to get to a point where we can
switch to naviserver internally. I'm still not there, so for me
there is more work to do.
> Slowl
19 matches
Mail list logo
