I guess also, functionality aside, its getting more important to be 1.1 compliant
to satisfy corporate requirements/policies.
i.e. one of our customers (quite a major one) insists on 1.1. compliance
for any web servers on their intranet. Therefore usefulness aside, 1.1. is
starting to become
Hmm, I haven't looked at the existing (pre 1.1) functionality in much detail,
so I can't really comment. I might get chance of the next day or two, but
can anyone else save me the trouble and confirm whether these things are
functionally equivalent?
Andrew Piskorski wrote:
[EMAIL PROTECTED]">
This reminds me: In anticipation of this week's chat, I've created a
page on the AOLserver Wiki with notes on the differences between
AOLserver 3.3.1+ad13+oacs1 and AOLserver 3.5.1. The page is based on
Rob's distribution notes for ad13. (Thanks Rob!) Corrections and
additions are very
- Original Message -
From: Rob Mayoff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, November 10, 2002 11:38 PM
Subject: Re: [AOLSERVER] HTTP 1.1 Pipelining.
HTTP/1.1 supports byte ranges. AOLserver 3.3.1+ad13 has support for
returning a byte range via fastpath and
In a message dated 11/11/02 2:30:48 AM, [EMAIL PROTECTED] writes:
Nathan,
I installed and configured it as you've described, but it's not working for me. There is nothing in the aolserver/stats directory. I'm assuming you have some adp's that are supposed to be put into the stats
On Monday, November 11, 2002, at 03:35 AM, Andrew Piskorski wrote:
pipelineing ... keepalive ...
What's the difference between the two?
I thought pipelining was the ability to send in more than one request
without waiting for the first to finish; responses are returned in order
of request.
On Sunday, November 10, 2002, at 11:43 PM, Jerry Asher wrote:
Why tabs?
If you are an emacs user, then the tab key means indent this line to the
proper level, and you don't care whether it uses tabs or spaces (but
spaces work out better on many printers).
If you use an editor for which the
Title: Message
I've made Nathan's stats
package available on a temporary server so you can get a look at
it.
Connect to
http://68.1.58.211:9049/_stats
user:
aolserver
pw:
stats
I'll leave it up for
today, and maybe tomorrow if you're interested. But this will save you the
trouble of
+-- On Nov 11, Patrick Spence said:
Hopefully if this is ever implemented it would be a toggleable item so we
aren't forced to have it available...
You could set up a preauth filter that removes Range header from ns_conn
headers. But I don't know why you'd want to disable it.
- Original Message -
From: Rob Mayoff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 11, 2002 8:50 AM
Subject: Re: [AOLSERVER] HTTP 1.1 Pipelining.
+-- On Nov 11, Patrick Spence said:
Hopefully if this is ever implemented it would be a toggleable item so
we
Very cool info! Thanks for the easy peek at them. -Jim
I've made Nathan's stats package available on a temporary server so you
can get a look at it.
Tcl arrays are associative. Tcl has pretty much 3 data structures:
- scalars
- lists
- arrays (which are associative)
The trick is that a list is really just a scalar with whitespace between
the elements, unless the element is enclosed by braces, so there's really
On Monday, November 11, 2002, at 01:22 PM, Jeff Hobbs wrote:
a list is really just a scalar with whitespace between
the elements
Woah, that last part isn't true at all, and is a common misconception
that leads people to think Tcl isn't up-to-snuff, which isn't true.
[snip]
That means that
On Mon, 2002-11-11 at 10:22, Jeff Hobbs wrote:
Tcl arrays are associative. Tcl has pretty much 3 data structures:
- scalars
- lists
- arrays (which are associative)
The trick is that a list is really just a scalar with whitespace between
the elements,
That means that list's lindex accessor is O(1) and appends are O(1)
except where we need to increase the C Tcl_Obj **objv array (and that
only needs to copy the pointers).
I'm happy to stand corrected regarding the implementation, but for someone
writing Tcl code, is there a meaningful
Lists are preserved in Tcl as arrays of Tcl_Obj's. If I do the
following:
proc makeList {size} {
set output
Is there any difference in initializing output to list at first, or is
there no difference. IOW, should I initialize 'output' to a list object,
or does
Now, if adding other scripting language support could be done without
adding any baggage to the core -- as external modules -- I'm all for it.
However, I would hate to see the core get bogged down with stuff to
accomdate all sorts of languages if it means negative impact towards its
ability
Creating a TCL-accessible array in a C module is trival. Just pass
the name of the TCL array variable to the C module, then in the C
code, do:
if (Tcl_SetVar2(interp, arrayname, subscript, val,
TCL_LEAVE_ERR_MSG) == NULL) {
return TCL_ERROR;
}
Args 2-4 are just simple strings. The
+-- On Nov 11, Peter M. Jansson said:
I'm happy to stand corrected regarding the implementation, but for someone
writing Tcl code, is there a meaningful difference between my flawed
conceptual model and the implementation?
{ is a string but not a list.
In a message dated 11/11/2002 2:18:32 PM Eastern Standard Time, [EMAIL PROTECTED] writes:
I wouldn't think that it would bog down the core if done right. Perhaps
a few extra hooks, but not many. Note that tclperl and tclpython both
exist and could assist in this respect (although we already have
Nate, what archive name/item# does this discussion belong?
Thx - A.
Nathan Folkman wrote:
In a message dated 11/11/2002 2:18:32 PM Eastern Standard Time,
[EMAIL PROTECTED] writes:
I wouldn't think that it would bog down the core
if done right. Perhaps
a few extra hooks, but not many.
I just loaded nsvhr/nsunix (with Dossy's patches) onto 3.51 and
it does not seem to recognize registered procedures correctly
'aolserver/modules/tcl' does get sourced, but I have to add a
port number to the virtual server to access /NS/Admin pages
Any procedures added in
- Now, if adding other scripting language support could be done without
- adding any baggage to the core -- as external modules -- I'm all for it.
- However, I would hate to see the core get bogged down with stuff to
- accomdate all sorts of languages if it means negative impact towards its
-
In a message dated 11/11/2002 5:03:21 PM Eastern Standard Time, [EMAIL PROTECTED] writes:
The real issue with integration is not language crosstalk, IMO -- that
is a more general problem that is being solved elsewhere (e.g. tclpython).
Hooking into the AOLserver internals so that Python, or Java,
On Mon, 11 Nov 2002 14:45:07 EST, Nathan Folkman [EMAIL PROTECTED] wrote:
The PHP model is kind of nice in that you can simply build it with support
for AOLserver, and it just installs all the right stuff. Internally, here at
AOL, there is a guy doing some integration work with Tomcat. He'll be
On 2002.11.11, Jeff Hobbs [EMAIL PROTECTED] wrote:
Tcl arrays are associative. Tcl has pretty much 3 data structures:
- scalars
- lists
- arrays (which are associative)
The trick is that a list is really just a scalar with whitespace between
the elements,
On 2002.11.11, Jeff Hobbs [EMAIL PROTECTED] wrote:
Ah ... Vignette. If I could find the people responsible for the original
design of the Vignette/Tcl integration, I would give them a good smack in
the head.
Come on, of all the commercial applications of Tcl, Vignette's probably
made the most
On 2002.11.11, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
I just loaded nsvhr/nsunix (with Dossy's patches) onto 3.51 and
it does not seem to recognize registered procedures correctly
'aolserver/modules/tcl' does get sourced, but I have to add a
port number to the virtual server to access
28 matches
Mail list logo
