Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Dossy Shiobara
On 2004.08.19, Wojciech Kocjan <[EMAIL PROTECTED]> wrote: > For returning files, you can always work the way [fcopy] does - leave > the fp open and when the socket is writable, read some more and send it. > > This wouldn't be too resource consuming. I've never seen too many HTML > files above 100K

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Wojciech Kocjan
Jim Wilcoxson wrote: IMO it is not scalable to use connection servicing threads to spool output when the size of the output exceeds the socket buffer capacity. Doing I/O with non-blocking, event-driven threads also helps prevent DOS attacks. The trade-off is in memory usage: when a connection serv

[AOLSERVER] AOLserver Project CVS Commit Guidelines

2004-08-18 Thread Dossy Shiobara
After the recent discussions, I felt it may be useful to codify what I see as the current CVS commit guidelines for project developers. The current text is up on the wiki: http://panoptic.com/wiki/aolserver/CVSCommitGuidelines I make reference to a "Vision Statement" which I am still in the

Re: [AOLSERVER] Progress report

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Michael Matthews <[EMAIL PROTECTED]> wrote: > On Aug 18, 2004, at 3:08 PM, Chris Davies wrote: > > > expected behavior yes. > > > > Actual behavior, no > > > > telnet aol.com 80 > > That would be because you're going to a redirect farm, not the actual > site. > > Try www.aol.com. Th

Re: [AOLSERVER] Progress report

2004-08-18 Thread Michael Matthews
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 18, 2004, at 3:08 PM, Chris Davies wrote: expected behavior yes. Actual behavior, no telnet aol.com 80 That would be because you're going to a redirect farm, not the actual site. Try www.aol.com. - -- Michael Matthews, [EMAIL PROTECTED] | TCAFTP

Re: [AOLSERVER] Progress report

2004-08-18 Thread Chris Davies
expected behavior yes. Actual behavior, no telnet aol.com 80 Trying 205.188.145.213... Connected to aolr-v1.evip.aol.com. Escape character is '^]'. HEAD / HTTP/1.0 HTTP/1.0 404 Not Found MIME-Version: 1.0 Date: Wed, 18 Aug 2004 19:04:18 GMT Server: AOLserver/3.4.2 Content-Type: text/html Content

Re: [AOLSERVER] Progress report

2004-08-18 Thread Noah Robin
On Aug 18, 2004, at 1:09 PM, Chris Davies wrote: It seems that a HEAD request is still processed by OpenACS, and even though it is a HEAD request, it does set up a session and set a cookie. As an FYI, the HTTP RFC basically states that servers should do all the processing on a HEAD request that wou

Re: [AOLSERVER] Progress report

2004-08-18 Thread Chris Davies
On Wed, 2004-08-18 at 09:22 -0400, Janine Sisk wrote: > Based on suggestions here, I set minthreads to 10 and threadtimeout to > 3600. Maxthreads was already set to 10, so I left it alone. You mention OpenACS -- I had a server that got bogged down tremendously the other day when it got hit with a

Re: [AOLSERVER] QOS

2004-08-18 Thread Jim Wilcoxson
> > figure out where Google's robots live. That's why I was suggesting > > that the dispatching algorithm needs to be a registered proc. > > Perhaps it could be both. Yeah, that would be nice. No doubt many people would want to group just by URL, and that would solve several of the cases I raise

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Zoran Vasiljevic
On Wednesday 18 August 2004 16:43, Robert Seeger wrote: > Given the current movement of this thread in the direction of "You're > wrong... no, you are!!", I figured I'd toss something out in an attempt > to set it back on track a bit. > > What, exactly, is the goal that we are trying to accomplish

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Jim Wilcoxson
... > > AOLserver is ideally suited to the majority of server tasks. About the > > only shortcoming which comes to mind is that conn threads are required > > to do blocking writes. But fixing that would be of benefit to the HTTP > > processing side too. > > So, we want reader threads and separate

Re: [AOLSERVER] QOS

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Jim Wilcoxson <[EMAIL PROTECTED]> wrote: > Hi - To put spiders in a separate thread pool, mapping requests to > thread pools by url doesn't work. You have to map by regular > expression on the User-Agent header or by IP address, assuming you can > figure out where Google's robots li

Re: [AOLSERVER] Progress report

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Janine Sisk <[EMAIL PROTECTED]> wrote: > On Aug 18, 2004, at 9:47 AM, Dossy Shiobara wrote: > > >What class of hardware are these sites running on? maxthreads=10 is > >pretty low, IMHO. Running one site on a 1.2 GHz P3 running Linux, I'd > >comfortably set minthreads=maxthreads=30.

Re: [AOLSERVER] Progress report

2004-08-18 Thread Jim Wilcoxson
maxconnections should be high, like 100. This is the number of keepalive socket connections your server maintains. These are low overhead, and make it faster for active browsers to get pages from you site since they don't have to reconnect. We use a keepalive timeout of 15 (seconds). That means

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Robert Seeger
Given the current movement of this thread in the direction of "You're wrong... no, you are!!", I figured I'd toss something out in an attempt to set it back on track a bit. What, exactly, is the goal that we are trying to accomplish by applying one of these patches? Can we put together a list of g

Re: [AOLSERVER] Progress report

2004-08-18 Thread Jim Wilcoxson
Hi - a few suggestions/ideas: 1. How many requests per second do you average, and what are your burst rates like? What are your vmstat numbers like during average and burst request processing, and how do they compare to when your system is lightly loaded? Getting familiar with these numbers will

Re: [AOLSERVER] Progress report

2004-08-18 Thread Janine Sisk
On Aug 18, 2004, at 9:47 AM, Dossy Shiobara wrote: What class of hardware are these sites running on? maxthreads=10 is pretty low, IMHO. Running one site on a 1.2 GHz P3 running Linux, I'd comfortably set minthreads=maxthreads=30. BTW, what's the guidelines on setting maxconnections? Should it b

Re: [AOLSERVER] QOS

2004-08-18 Thread Jim Wilcoxson
Hi - To put spiders in a separate thread pool, mapping requests to thread pools by url doesn't work. You have to map by regular expression on the User-Agent header or by IP address, assuming you can figure out where Google's robots live. That's why I was suggesting that the dispatching algorithm

Re: [AOLSERVER] Progress report

2004-08-18 Thread Janine Sisk
On Aug 18, 2004, at 9:47 AM, Dossy Shiobara wrote: What class of hardware are these sites running on? maxthreads=10 is pretty low, IMHO. Running one site on a 1.2 GHz P3 running Linux, I'd comfortably set minthreads=maxthreads=30. Dual 733 MHz P3s, old Dell server running Linux. I can (and will)

Re: [AOLSERVER] nsopenssl errors

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Janine Sisk <[EMAIL PROTECTED]> wrote: > To add a bit more data to the fire, here is the config section I was > using for nsopenssl with AOLserver 4. it is basically straight out of > the latest version of the OpenACS suggested config file. > > The *.pem files do exist; I believe I

Re: [AOLSERVER] Progress report

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Janine Sisk <[EMAIL PROTECTED]> wrote: > To refresh everyone's memory, I have a situation where a couple of > older ACS sites on the same system, running nsd3.3+ad13, started > hanging multiple times per day. Most of the time by the time I receive > notification from uptime, the pro

Re: [AOLSERVER] nsopenssl errors

2004-08-18 Thread Bruno Mattarollo
Hello Dossy, On Aug 18, 2004, at 20:56, Dossy Shiobara wrote: ns_param CertFile server/server.crt ns_param KeyFile server/server.pem Do these two certificate files exist? In the server log at start-up, does it say it was able to load these okay? If it can't load them, t

[AOLSERVER] Progress report

2004-08-18 Thread Janine Sisk
To refresh everyone's memory, I have a situation where a couple of older ACS sites on the same system, running nsd3.3+ad13, started hanging multiple times per day. Most of the time by the time I receive notification from uptime, the problem has passed and leaves no clue behind. Sometimes I do man

Re: [AOLSERVER] nsopenssl errors

2004-08-18 Thread Janine Sisk
To add a bit more data to the fire, here is the config section I was using for nsopenssl with AOLserver 4. it is basically straight out of the latest version of the OpenACS suggested config file. The *.pem files do exist; I believe I changed the client cert section to point to the same files as t

Re: [AOLSERVER] nsopenssl errors

2004-08-18 Thread Dossy Shiobara
On 2004.08.18, Bruno Mattarollo <[EMAIL PROTECTED]> wrote: > > I have been following quite closely the discussion about nsopenssl 3.0 > beta and AOLServer 4 and after several weeks of working with nsopenssl > 3.0 beta 18, AOLServer 4.0.5, OpenSSL 0.9.7d I saw this in the error > logs (when I put de

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Zoran Vasiljevic
On Tuesday 17 August 2004 22:25, Dossy Shiobara wrote: > No, we should NOT apply EITHER of these two multi-protocol patches, > > BECAUSE ... the entire driver model is being reworked for 4.1. Can > the same functionality be implemented against 4.1 without getting in > the way of the re

Re: [AOLSERVER] Support for non-HTTP protocols

2004-08-18 Thread Bernd Eidenschink
> a. YES, I like AS to be more powerful multiprotocol > server instead of being a powerful http-server only. > And, I like proposal X better than Y because of Z. I vote for (a). I read both discussions from the sourceforge-links you provided and I see no "jealousness" or "vanity" betw

[AOLSERVER] nsopenssl errors

2004-08-18 Thread Bruno Mattarollo
Hello, I have been following quite closely the discussion about nsopenssl 3.0 beta and AOLServer 4 and after several weeks of working with nsopenssl 3.0 beta 18, AOLServer 4.0.5, OpenSSL 0.9.7d I saw this in the error logs (when I put debug to "true" in my nsd.tcl) [18/Aug/2004:16:57:38][805.251873