From an OpenACS users point of view who is also working closely
with ]po[, probably the major reason for AOLserver installations
nowadays, I just want this to work and easy to install. I assume the
module will also work on the Windows Version? I furthermore assume
the module does not have a
: Monday, October 01, 2007 12:36 PM
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] ns_conn channel, ns_conn contentsentlength
On 2007.10.01, Jeff Rogers <[EMAIL PROTECTED]> wrote:
> I also think the code belongs on a module rather than in the core.
My vote is to leave [ns_conn channel
On Monday 01 October 2007 12:35, Dossy Shiobara wrote:
> My vote is to leave [ns_conn channel] in the core officially, and mark
> [ns_conn contentsentlength] as deprecated to warn folks from coupling
> their code too tightly to it, as it may be removed in a future version.
Personally I don't think
On 2007.10.01, Jeff Rogers <[EMAIL PROTECTED]> wrote:
> I also think the code belongs on a module rather than in the core.
My vote is to leave [ns_conn channel] in the core officially, and mark
[ns_conn contentsentlength] as deprecated to warn folks from coupling
their code too tightly to it, as i
Well there are some surprising things in this change. I'm not sure what the
spliceout variable means, but it is unrelated to the Ns_ and Tcl_ spliceout
functions, and I have no idea what they do yet.
But the nContentSent (and sock) member is private to a Conn, not even visible
in a Ns_Conn, so
On 2007.10.01, Tom Jackson <[EMAIL PROTECTED]> wrote:
> On the surface, the patch appears (as described) to do something like
> ns_returnfile. All the patch does is to make a copy of the connection
> and wrap the sock in a Tcl_Channel.
My only real concern about the change:
What happens if you tr