Don Baccus wrote:
On Jun 6, 2011, at 12:25 PM, Andrew Piskorski wrote:
In general, I don't think the ACS/OpenACS 4.x request processor
design was EVER carefully thought out with respect to all of
AOLserver's features and use cases.
Or, in this case, didn't understand the bug that the
A thought for an alternate way to handle this - if the content-length is
too large, the just don't read the content, but set an error flag on the
conn. That way, an adventurous system could return a custom error page,
or even handle reading the content through custom code. I think this
could
Jim Davidson wrote:
I think today, in 2011, some of the flexibility we imagined back in
1995 isn't really so needed. This includes general purpose logging
plugins and network drivers when there really is just the common log
format, ordinary and SSL sockets. More in the core for the base HTTP
Maurizio Martignano wrote:
Well… ehm... the version in the tar ball compiles and runs well under
Windows…
Not so for the version under CVS HEAD: many of the changes introduced
have been implemented with a careful eye only for *nix, and not for Windows.
By looking at the code I have the
Dossy Shiobara wrote:
It's probably safer to define this as SOCKET, but windows.h says
SOCKET is:
The source comment is misleading, because trigger is set up as a socket
pair, not as a pipe. Not sure why it's this way, but there it is. And
ns_sockpair is already prototyped as
Maurizio,
I think we're all in agreement at this point. Could you put together a
patch?
-J
Maurizio Martignano wrote:
Don
In Aolserver source code
95% of more of the times sockets are declared as SOCKET; the other times as
int.
This is an inconsistency and is a fact.
If you wanted to
Hi all,
I'm implementing a minor enhancement to the adp parser to make null end
tags (aka empty elements or minimized tags) work. Or more simply, if
you have a registered adp tag where the end tag matches the opening tag,
then rather than
mytag name=value/mytag
you can simply write
mytag
Another thing you could do is to set tcl's default encoding to utf-8, so
that the filenames passed to Ns_ConnReturnFile are the same encoding as
what the core tcl commands do.
Set the default encoding with
encoding system utf-8
in some tcl file. It's possible this could have some side
Klaus Hofeditz ]project-open[ wrote:
I gave it a try since some of our users do upload files using tools
such as WINSCP. Since these files would also need to be accessible
through the ]project-open[ file manager, we need to come up
with a slightly more complex solution to detect files with
Thorpe Mayes wrote:
Hi,
I am trying to install the solid database drivers and cannot do it.
I am running aolserver 4.5.0.
I added the nssolid_3.0 driver. I then added solid-fix.tar, which updated the
Makefile file and added the nssolid.h file to the nssolid directory.
Where is
Hey all, me again.
For those of you who don't monitor the commits list I wanted to share a
few changes I've recently made as well as a few I'm still thinking about.
- implemented native decoding of strings in ns_returnfile. This allows
filenames that are not utf-8 to be passed, similar to
Sourceforge seems a reasonable choice to me.
-J
Dossy Shiobara wrote:
Everyone,
It appears that AOL is going to be shutting own its LISTSERV, which
includes several AOLserver mailing lists.
Since there's still activity on this mailing list, I think it would be
worth moving to a new list.
Fenton, Brian wrote:
Hi Jeff
congrats on all the great work. That all sounds super. A new
AOLserver release would be amazing, but maybe seeing as 4.0 was first
released 8 years ago, we could consider that it's about time for a
move to 5.0? Not wanting to get too Firefox-y about it, but I think
Brett Schwarz wrote:
I'll grab the latest and greatest from SF and start messing around with
your changes. Is SF the main repo for aolserver? What about the modules
(specifically nspostgres)?
Yep, SF is still the place for aolserver and nspostgres (which looks
like it has been updated to
I think from the tcl perspective the interp management is interesting.
Interps are initialized with a startup script (created through
introspection) and reused by multiple requests without reinitializing
(cleaned up after each request, again using introspection).
-J
Matthew M. Burke wrote:
Daniël Mantione wrote:
Maybe I could point again at the ipv6 patch I wrote in 2008. Back there
was even not even a response on this list, but maybe today, now the
world has run out of ipv4 addresses, the interrest in serving ipv6 is a
bit higher.
Patch still available for download here:
I had problems starting at the exact same time but on Solaris, where
they manifested as a EINVAL return from pthread_cond_tomedwait. After a
day of tracing the problem with debug builds and working with my
sysadmin to track what changed (of course, nothing had) I cam to the
same 1 billion
dhogaza@PACIFIER.COM wrote:
I have three servers running identical installations of
AOLserver/3.3.1+ad13. On two (development and production, very low and
relatively low traffic volumes respectively) all scheduled procs have
stopped firing.
My God, it sounds to me like you're all being
in a nicer manner, but that
problem won't affect anyone for years :)
-J
Janine Sisk wrote:
On May 19, 2006, at 1:04 PM, 'Jesus' Jeff Rogers wrote:
The only bug is that Ns_CondTimedWait doesn't do any wraparound on the
time parameter. All the same, I've been enjoying telling people that
I hit
Stan Kaufman wrote:
Which coincidentally is the expiry time (MaxOpen and MaxIdle) set on
my database connections. My system is ACS-derived, so I wouldn't be
surprised if these database settings are common in other ACS-derived
systems.
What do you think is the reason that not all systems
John Buckman wrote:
Right restarting is not something I like to doing, because most of the
time when I ctrl-c aolserver, it exists uncleanly with one of these errors:
Would it work any better/more reliably to have aolserver exit itself, by
calling ns_shutdown and hopefully allowing any
Daniël Mantione wrote:
Ok, practical example:
We have a server, two users want to run OpenACS, and 20 users simply
wants to code PHP/MySQL. Proposal to the system administrator: Put pound
on Port 80 and have requests for the two OpenACS users redirected to their
own AOLserver process.
Now,
Don Baccus wrote:
On Apr 12, 2008, at 8:46 AM, Brett Schwarz wrote:
For *my* application, I would have the config params do the decision
almost all of the time. However, I concede that other people's use
cases may be different...so I think a hook into the compression
decision making from
101 - 123 of 123 matches
Mail list logo
