Re: [AOLSERVER] AOL Listserv to be Discontinued

2011-10-26 Thread Jim Davidson
Dossy: Thanks for handling this! -JIm On Oct 26, 2011, at 9:43 AM, Dossy Shiobara wrote: Hi, There has been little discussion or response to this matter, and the few responses have all been in favor of moving the lists to SourceForge. Today is the 26th, so I'd like to do the list move

Re: [AOLSERVER] Discussing AOLserver at the Tcl/Tk conference

2011-10-25 Thread Jim Davidson
Agreed -- this has always been one of the must unique and/or goofy aspects of AOLserver and Tcl. I gave the keynote at the 7th (yes, 7th!) tcl/tk conference years ago: http://www.aolserver.com/docs/intro/tcl2k/ You could mention how this work has continued on and off over the years.

Re: [AOLSERVER] recent updates

2011-10-25 Thread Jim Davidson
Hi, Cool! Nice updates :) On the version # question a few days back, I agree this is 4.x update. For a 5.x release, in addition to what you listed below, I'd add: -- integrate SSL support directly (comm driver, api's) -- integrate the comm drivers -- figure out some better build environment

Re: [AOLSERVER] recent updates

2011-10-25 Thread Jim Davidson
Good catch -- trying to get IP6 working makes sense as well. -Jim On Oct 25, 2011, at 3:54 PM, Daniël Mantione wrote: Op Tue, 25 Oct 2011, schreef Jim Davidson: Hi, Cool! Nice updates :) On the version # question a few days back, I agree this is 4.x update. For a 5.x

Re: [AOLSERVER] Fwd: AOLserver 4.5.0 - ns_returnfile does not find file - file name contains special chars

2011-09-22 Thread Jim Davidson
Howdy, Looking at the code, ns_returnfile passes the filename through to the core Ns_ConnReturnFile without any of the care that core Tcl does handling filenames. You may be able to replace ns_returnfile with ns_returnfp, passing a file handle returned from Tcl's open command which should be

Re: [AOLSERVER] Aolserver Progress - Some few examples.... - Errata Corrige

2011-08-06 Thread Jim Davidson
I vaguely remember never figuring this out either and deciding to ifdef it out. In practice it doesn't do much -- I've never come across a on-exit handler that really needed fire. Curious if anyone has. Jim Sent from a phone On Aug 6, 2011, at 3:29 PM, Maurizio Martignano

Re: [AOLSERVER] Progress in Aolserver

2011-08-05 Thread Jim Davidson
if you want to spread the users base of your OpenACS/Aolserver based application, having it running also on Windows may be very helpful. Cheers, Maurizio -Original Message- From: AOLserver Discussion [mailto:AOLSERVER@LISTSERV.AOL.COM] On Behalf Of Jim Davidson Sent: 03 August

Re: [AOLSERVER] Aolserver Progress - Some few examples....

2011-08-04 Thread Jim Davidson
Hi It's a socket so it can be monitored by select and poll. It should be SOCKET, I think it was in the past. On windows lib-c file handles returned by _open aren't the same as sockets. You can see this in the libc source Microsoft provides. They can't be monitored with select. The

Re: [AOLSERVER] Aolserver Progress - Some few examples....

2011-08-04 Thread Jim Davidson
Hi, I'm looking at the code now -- definitely needs to be SOCKET in nsd.h. The reason can be seen in ns_sockpair in fd/sock.c where the code for a socket pair is done. It's just a wrapper around Unix socketpair() but has a bunch of extra code to do the loopback-connect thing on Windows. The

Re: [AOLSERVER] adp null end tags

2011-08-04 Thread Jim Davidson
Sounds good to me. -Jim On Aug 4, 2011, at 4:21 PM, Jeff Rogers wrote: 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

Re: [AOLSERVER] Progress in Aolserver

2011-08-03 Thread Jim Davidson
for the Windows support in AOLserver -- once upon a time, I had built the Windows binaries that some folks were using. Through discussions I had with Jim Davidson, the new build mechanism for AOLserver 4.5.x was meant to make building AOLserver on Windows easier than it had been in the past. I

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-24 Thread Jim Davidson
Cool. The driver thread is technically a single threaded thing which shouldn't block and the connection return functions are blocking but as the response is small, it probably just works. Also, the connection code hasn't been verified to run in the driver (filters, traces, etc.) but again it

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
Hi, The short answer is no, there's no access log entry although there may be a server log message buried in the chatter. The reason is the access log is a trace that fires at the end of an HTTP connection and the request isn't a connection until all the content has been read and the data

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
@LISTSERV.AOL.COM] On Behalf Of Jim Davidson [jgdavid...@mac.com] Sent: 23 June 2011 13:47 To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] Problem with file uploads larger than maxinput Hi, The short answer is no, there's no access log entry although there may be a server log message

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
to handle the request -- but, the driver thread still makes sure that the hard limits are enforced on the request that will be passed on to the conn thread ... ? On 6/23/11 8:47 AM, Jim Davidson wrote: The reason is the access log is a trace that fires at the end of an HTTP connection

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
] On Behalf Of Jim Davidson [jgdavid...@mac.com] Sent: 23 June 2011 14:44 To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] Problem with file uploads larger than maxinput Howdy, Appears you need to set driver debug mode for the driver for the given socket module thing

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
Agreed. Should go on the bug/feature list. Is there a list ? :) Sent from a phone On Jun 23, 2011, at 9:58 AM, Dossy Shiobara do...@panoptic.com wrote: Yes, on E_CRANGE, the driver thread should return HTTP 413 Request too large, IMHO. And, we should be able to configure a custom response

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-06-23 Thread Jim Davidson
I think this one case can be handled this way because you could truncate the request (some content may have been read ahead) and then flag it for special handling in the normal connection processing code/threads. The reason is the server has a full request, you're just choosing to not read all

Re: [AOLSERVER] How to use connection functions from libnsd.so

2011-06-19 Thread Jim Davidson
You can use normal Tcl or aolserver socket functions but the core server listening and http processing is too low level to expose via Tcl. Was always a good idea, eg a Tcl command that creates a server instance, but would require a lot of refactoring the core. Jim Sent from a phone On Jun

Re: [AOLSERVER] hacking around

2011-06-03 Thread Jim Davidson
Howdy, I still watch the list but haven't had time to dig into the code in a long time -- maybe later this summer :) Anyway, these connection filters are a bit confusing and not well documented -- my fault. Here I think it's ok to not call the filters again but it could go either way. If

Re: [AOLSERVER] upload progress

2010-02-04 Thread Jim Davidson
The method of checking progress on a separate URL similar to the example I sent does result in repeated requests during upload. But, they're trivial by comparison - easily in the 100's of req/sec range of response time and throughput. A bit goofy, but over a single keep- alive socket for

Re: [AOLSERVER] upload progress

2010-01-23 Thread Jim Davidson
design principles we had in AOLserver. Interesting to see how this has evolved over 15 years (some of the first code for multithreaded AOLserver appeared in early 1995 -- I had more hair then). -Jim tom jackson On Mon, Dec 7, 2009 at 8:21 PM, Jim Davidson jgdavid...@mac.com wrote: Hi

Re: [AOLSERVER] upload progress

2010-01-21 Thread Jim Davidson
Hi, I think we were talking about this about a month ago. I updated the source to enable upload-progress checking with a combination of ns_register_filter and nsv -- there's an example at the latest ns_register_filter man page (pasted below). This may work for you although it would require

Re: [AOLSERVER] upload progress

2009-12-08 Thread Jim Davidson
connection gets running. -Jim On Dec 1, 2009, at 4:45 PM, Jeff Rogers wrote: Jim Davidson wrote: Right -- the pre-queue thing operates within the driver thread only, after all content is read, before it's dispatched to a connection. The idea is that you may want to use the API to fetch using

Re: [AOLSERVER] large file uploads

2009-12-01 Thread Jim Davidson
Howdy, Looking back at the code and trying to remember what I was thinking at the time, I ran across the header comment to NsConnContent which mentions the possibility of a mapping failure (see below). This reminded me of what was going on... Originally there was no spool to file option --

Re: [AOLSERVER] upload progress

2009-12-01 Thread Jim Davidson
Right -- the pre-queue thing operates within the driver thread only, after all content is read, before it's dispatched to a connection. The idea is that you may want to use the API to fetch using event-style network I/O some other bit of context to attach to the connection using the connection

Re: [AOLSERVER] upload progress

2009-12-01 Thread Jim Davidson
On Dec 1, 2009, at 4:45 PM, Jeff Rogers wrote: Jim Davidson wrote: Right -- the pre-queue thing operates within the driver thread only, after all content is read, before it's dispatched to a connection. The idea is that you may want to use the API to fetch using event-style network I/O some

Re: [AOLSERVER] is it necessary

2009-11-02 Thread Jim Davidson
be as great and efficient as AOLserver is, but it will be a whole lot easier for people to use and sell to fellow staff, management, clients, etc. Just my thoughts on the subject! (And I do realise this is a whole lot of work!) Bas. On 28/10/2009, at 12:34 PM, Jim Davidson wrote

Re: [AOLSERVER] is it necessary

2009-10-30 Thread Jim Davidson
With fancy switches and/or proxies like varnish can you effectively blend aolserver with other app servers (lamp, ruby etc) now without actual code changes ? I'm wondering if folks have done that successfully Jim Sent from my iPhone On Oct 27, 2009, at 6:55 PM, Dossy Shiobara

Re: [AOLSERVER] Aolserver as multithreaded TCL soc ket server ?

2009-08-22 Thread Jim Davidson
The code should work ok. I remember it was a bit messy to map these Aolserver tcl commands which pre-dated the Tcl channel stuff so it was compatible years ago and there were examples of memory leaks from long running detached tcl threads but with care it should be ok Jim Sent from my

Re: [AOLSERVER] Question on two AOLserver tickets

2009-05-15 Thread Jim Davidson
Hi, I'm looking at the head code and it appears it's now safe -- the connection list is walked with a pool lock held and the request data (method, url) seem to be copied with a global reqlock mutex held. Jade: What version of AOLserver are you using? -Jim On May 15, 2009, at 10:06

Re: [AOLSERVER] Question on two AOLserver tickets

2009-05-14 Thread Jim Davidson
Hi, Do you have some sort of background job that calls ns_server active (or similar) regularly? That could lead to random crashes. The description in http://dev.aolserver.com/trac/ticket/152 is accurate: The code, by design, is not strictly safe as it's assumed to only be used

Re: [AOLSERVER] Question on two AOLserver tickets

2009-05-14 Thread Jim Davidson
to it, is prohibited. On Thu, May 14, 2009 at 10:19 AM, Jim Davidson jgdavid...@mac.com wrote: Hi, Do you have some sort of background job that calls ns_server active (or similar) regularly? That could lead to random crashes. The description in http://dev.aolserver.com/trac/ticket/152 is accurate

Re: [AOLSERVER] Question on two AOLserver tickets

2009-05-14 Thread Jim Davidson
, at 12:33 PM, Jim Davidson wrote: Yup -- should really have been documented better -- sorry about that. Anyway, what is the monitoring attempting to dig up? There may some other safe ways to get the same. -Jim On May 14, 2009, at 2:04 PM, Jade Rubick wrote: Ironically, we have some

Re: [AOLSERVER] missing access log entries

2009-04-15 Thread Jim Davidson
Hi, I haven't been able to test myself but the changes make sense to me too. Thanks Tom! -Jim On Apr 15, 2009, at 6:52 AM, Gustaf Neumann wrote: Dear Tom, your rewrite of the two functions below look fine to me. The structure is much clearer now, results of the authorization handling are

Re: [AOLSERVER] missing access log entries

2009-04-15 Thread Jim Davidson
I'm wondering if there needs to be some more specific exception flags stored in the connection structure to handle all these cases and some C and Tcl api's to access/modify the same. It seems you're doing the good work of rationalizing all the error conditions that had been pretty

Re: [AOLSERVER] missing access log entries

2009-04-14 Thread Jim Davidson
going on now). -Jim On Apr 13, 2009, at 2:48 PM, Tom Jackson wrote: On Mon, 2009-04-13 at 13:49 -0400, Jim Davidson wrote: Hi, A bit old but let me try to be helpful here... On Apr 3, 2009, at 11:45 PM, Tom Jackson wrote: Jim, Thanks for adding some back story. Over the weekend

Re: [AOLSERVER] missing access log entries

2009-04-13 Thread Jim Davidson
Hi, A bit old but let me try to be helpful here... On Apr 3, 2009, at 11:45 PM, Tom Jackson wrote: On Fri, 2009-04-03 at 16:20 -0600, Jim Davidson wrote: HI, Sorry -- I wrote the original and goofy code leading to this confusion... Thanks for monitoring our head scratching! I have

Re: [AOLSERVER] missing access log entries

2009-04-03 Thread Jim Davidson
HI, Sorry -- I wrote the original and goofy code leading to this confusion... Based on this discussion I think it's NOT working as intended. If there was a time I thought ns_adp_abort should mean return NS_ERROR for connection status and thus no-traces... I've long since forgotten

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-22 Thread Jim Davidson
Caruso wrote: On Thursday 02:34 PM 8/21/2008, Jim Davidson wrote: To clarify one point: There is no technical solution to creating temp files with the same name and avoiding the race condition without additional synchronization. To clarify as well: the original code didn't involve a race

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-21 Thread Jim Davidson
Hi, Yes -- the original reason for dev/inode on Unix instead of filename was to reduce memory consumed in the case of a large # of symlinks or hardlinks to the same file. This was the case for AOL's digitalcity.com back in 1999. For better or worse, the AOL in AOLserver means AOL was

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-20 Thread Jim Davidson
was introduced for scrambling NFS vnodes. -Jim On Aug 20, 2008, at 12:54 PM, John Caruso wrote: On Wednesday 08:45 AM 8/20/2008, Jim Davidson wrote: Overall, it seems one thing to do would be to switch to filename- based cache keys by default, leaving the dev/inode pair as an option for folks who

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-20 Thread Jim Davidson
Hi Folks, I agree with Eric, even though I wrote the original code and was one of the first to suggest is wasn't a bug. This thread has surprised me in a few ways: -- The bug was indeed subtle and curious -- The debate on dynamic vs. static and underlying assumptions and performance was

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-19 Thread Jim Davidson
Hi folks, I wrote the code. The explanation below is correct -- I chose inode/ dev combination to cache the same file even with multiple names which was the case at AOL -- hundreds of symlinks and hard links to the same file. The same strategy is used for ADP templates. I think the

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-19 Thread Jim Davidson
Hi, I haven't looked at a directory change notification type scheme in a long time but that could be very clever. Aside from addressing issues discussed here, the key benefit would be to avoid the repeated stat syscalls. Those stat calls always bothered me conceptually but the

Re: [AOLSERVER] Data corruption with fastpath caching

2008-08-19 Thread Jim Davidson
a dynamic app using files should use open/cached fd's). -Jim On Aug 19, 2008, at 9:25 PM, John Caruso wrote: On Tuesday 05:39 PM 8/19/2008, Jim Davidson wrote: Your right, the code snippet below could trip over a race condition as you've described. It's not a race condition, actually

Re: [AOLSERVER] ns_share (was Active participation)

2008-04-16 Thread Jim Davidson
Hi, Brent Welch wrote some ns_share code which worked with Tcl variable traces to emulate the original code. It works except for a few edge cases but is generally considered less efficient and flexible than the new nsv_* commands. So, when I say we gave up on ns_share I mean we

Re: [AOLSERVER] AOLserver 4.5.0 on windows not exiting service

2008-04-11 Thread Jim Davidson
Hi, I don't think you lose anything -- Tcl_Finalize carefully tears everything down which is good when the code is used in an embedded system but in AOLserver as a normal process on Unix or Windows the resulting _exit doesn't care about all the work Tcl_Finalize may have done. -Jim

Re: [AOLSERVER] how do I

2008-03-20 Thread Jim Davidson
There's an ns_internalredirect Tcl command which calls the Tcl_ConnRedirect C function -- maybe that does the right thing. I suppose you could also use ns_register_adp to map the URL to an ADP file instead of using ns_register_proc -- the ADP could then do the login and include guts

Re: [AOLSERVER] Google Summer of Code

2008-02-29 Thread Jim Davidson
Agreed :) Most of AOLserver core is ok being loaded into core Tcl although the server config and module/Tcl init framework incompatible. It can be made to work but old-style AOLserver modules would need to be updated. -Jim On Feb 28, 2008, at 6:53 PM, Jeff Hobbs wrote: Matthew M.

Re: [AOLSERVER] nsdci query

2007-10-27 Thread Jim Davidson
Howdy, I wrote the core SOB code years ago -- at the time I think our goals included: -- Security: Server connects out to known clients. -- Performance: State-full connections, minimal protocol overhead, lots of caching, no encoding overhead -- Simple: String keys, string data,

Re: [AOLSERVER] New modules on aolserver.am.net; also we are looking to hire a full-time AOLserver programmer

2007-09-27 Thread Jim Davidson
This reminds me of the Smarty for PHP. Has anyone looked at porting Smarty to ADP? It's pretty PHP-specific but the syntax, like Tom's stuff below, is pretty convenient. http://smarty.php.net/ -Jim On Sep 25, 2007, at 10:50 AM, Tom Jackson wrote: Jeff, I developed a templating

Re: [AOLSERVER] aolserver focus

2007-08-09 Thread Jim Davidson
Hi, After reading through all the responses to my aolserver focus post, it seems to me Thorpe's comments below are the most realistic and actionable, i.e., it's the documentation / getting started stuff that's insufficient. Otherwise, technically there are a few things that could be

[AOLSERVER] aolserver focus

2007-08-03 Thread Jim Davidson
Howdy folks, Seems like we're having another flare-up of frustration on the list... I left AOL about a year ago and haven't had much time to contribute since. I probably wrote (re-wrote and wrote again) 90% of the code and had several teams hacking Tcl code for dozens of AOL web sites

Re: [AOLSERVER] crash in AOLServer 4.5.0, after exiting threads

2006-11-01 Thread Jim Davidson
Hi, I think this is related to the comment I added to the RELEASE notes: * Loading libnsd into a tclsh and then creating new threads with the ns_thread command will result in a crash when those threads exit. The issues has to do with finalization of the async-cancel context used to support the

[AOLSERVER]

2006-07-06 Thread Jim Davidson
Hi, I just checked in a fix for this -- try again and let me know if it's still broken. -Jim On Jul 6, 2006, at 9:18 AM, Nathan Folkman wrote: If you haven't already, would you mind filing this as a bug against 4.5 over at SourceForge? I set up a new category for 4.5 bugs. I'll try to

Re: [AOLSERVER] New release?

2006-06-26 Thread Jim Davidson
Hi, If I remember correctly, the issue was linking aolserver 4.5 with the Tcl provided by FC5? The result was an error with multiple defined _init? I tried to reproduce this but couldn't locate the tclConfig.sh for the Tcl in FC5 required by the configure script. As Nate mentioned,

Re: [AOLSERVER] New release?

2006-06-22 Thread Jim Davidson
Hi,Here's what we've got on 32bit systems:sizeof(char) = 1sizeof(short) = 2sizeof(int) = 4sizeof(long) = 4sizeof(void *) = 4On 64bit we've got:sizeof(char) = 1sizeof(short) = 2sizeof(int) = 4sizeof(long) = 8sizeof(void *) = 8i.e., int is always 4 bytes, long is the size of a pointer and is either

Re: [AOLSERVER] AOLServer 4.0.10 and Mac OS X 10.4.6

2006-06-02 Thread Jim Davidson
I just checked in the fix which is really just to disable the configure check for poll on OS/X, thus not setting the HAVE_POLL cdef and defaulting to the poll emulation code used on OS/X in the past. So, update, re-config, and rebuild -- should work now. For those curious, it appears that

Re: [AOLSERVER] AOLserver 4.0(.10) memory usage

2006-06-02 Thread Jim Davidson
Folks, Nate and I spent a lot of time -- frankly, far too much time -- chasing this down a few months back. We ended up completely re- writing the multi-threaded allocator with features to reclaim memory, fix stats counters which in the current code are broken and lie, and added an alloc

Re: [AOLSERVER] Embed Tcl inside registered ADP tag?

2006-06-02 Thread Jim Davidson
... (result of Tcl) ... /mytag Steve, Yes, the order in which tags are parsed was changed between 3.x and 4.0.x, unfortunately. Jeremy Collins filed an RFE to change it back in September 2004, but it hasn't been done yet: http://aolserver.com/sf/rfe/1030577 Jim Davidson tells me he made

Re: [AOLSERVER] Batteries included AOLserver distribution

2005-08-25 Thread Jim Davidson
Dynamic link is best -- there was a lot of effort recently to get all that working right recently, with modules as small stubs that call into the dll's located in the lib/ directory and such. -Jim On Aug 25, 2005, at 10:00 AM, Olaf Mersmann wrote: Another issue I am undecided on is

Re: [AOLSERVER] Build/installation complexity with AOLserver 4 (for package maintainers) (was Re: [AOLSERVER] Batteries included AOLserver distribution)

2005-08-25 Thread Jim Davidson
Nate's working on some config stuff as well -- would be good to coordinate the efforts and get it into the core distribution. -jim On Aug 25, 2005, at 9:52 AM, Olaf Mersmann wrote: * Jim Davidson [EMAIL PROTECTED] [050825 15:24]: *snip* 7. would also be good if something

Re: [AOLSERVER] Build/installation complexity with AOLserver 4 (for package maintainers) (was Re: [AOLSERVER] Batteries included AOLserver distribution)

2005-08-25 Thread Jim Davidson
Folks, OK -- so it sounds like we have the following goals: 1. sources need to be configurable and buildable in the source directory 2. final install location needs to be part of the config for all the - rpath junk 3. install/copy step needs to bypass the final install location and copy to

Re: [AOLSERVER] Build/installation complexity with AOLserver 4 (for package maintainers) (was Re: [AOLSERVER] Batteries included AOLserver distribution)

2005-08-25 Thread Jim Davidson
Ugh -- that thing was a mess and hard to maintain. Better to start over. -Jim On Aug 25, 2005, at 11:22 AM, Nathan Folkman wrote: On Aug 25, 2005, at 11:12 AM, Dossy Shiobara wrote: On 2005.08.25, Nathan Folkman [EMAIL PROTECTED] wrote: $ bin/tclsh84 ./nsconfig.tcl -debug -modules

Re: [AOLSERVER] Batteries included AOLserver distribution

2005-08-25 Thread Jim Davidson
Yup -- that's what I understood the question to be and agree, link against the dynamic libraries. -Jim On Aug 25, 2005, at 10:53 AM, Dossy Shiobara wrote: On 2005.08.25, Jim Davidson [EMAIL PROTECTED] wrote: Dynamic link is best -- there was a lot of effort recently to get all

Re: [AOLSERVER] Batteries included AOLserver distribution

2005-08-24 Thread Jim Davidson
Turns out I spent a lot of time getting those -rpaths and - install_name things to work :) Oh well. Anyway, seems like three cases: - Mac OS/X -- without -install_name, it burns in the current build directory -- I think install_name_tool can be used at install time to reset. - On

Re: [AOLSERVER] AOLserver 4.x ADP parser

2005-08-23 Thread Jim Davidson
Hi, The patch would need to be updated as the underlying code has changed. Otherwise, I'm inclined to just restore the previous behavior unless I'm missing something. Does anyone have a reason why the new behavior is preferred to the old or was this all just something I screwed up

Re: [AOLSERVER] access log getting wiped

2005-07-22 Thread Jim Davidson
The code, Ns_RollFile, is pretty set on no more than 999 files right now. And, In the case you actually have 999 files, it does a lot work shuffling them down. Perhaps it would be better to just have the default be the time format stuff which doesn't need to do all the shuffling in the

Re: [AOLSERVER] Server not stopping properly

2005-07-19 Thread Jim Davidson
This should be in the code now -- check the shutdownPending static var in nsd/sched.c. The behavior should be that as soon as shutdown begins, this flag is set an no new sched procs can be created or kicked off. There could be a bug in there. Of course if a thread-based proc is running

Re: [AOLSERVER] Thread safe version of Ns_ConnReturnOpenFd()?

2005-07-18 Thread Jim Davidson
Hi, You're right -- it's not thread safe. Two options: 1. Add the offset length parameters and have the server use pread as you suggest (not sure about the equivalent on win32). I suppose this would technically not be backward compatible in case someone was expecting the current seek

Re: [AOLSERVER] Thread safe version of Ns_ConnReturnOpenFd()?

2005-07-18 Thread Jim Davidson
the other code changes including some routines to get at the uploaded files in C -Jim On Jul 18, 2005, at 5:11 PM, Fred Cox wrote: --- Jim Davidson [EMAIL PROTECTED] wrote: Hi, You're right -- it's not thread safe. Two options: 1. Add the offset length parameters and have the server

[AOLSERVER] Checked in some code

2005-07-18 Thread Jim Davidson
Hi, I just checked in several changes to the 4.5 HEAD branch. The ChangeLog was updated with some notes. Briefly: - Finished up support for large content in temp-files. - Added new routines to access uploaded files in C, e.g., Ns_ConnGetFile - Added a new ns_cache command based on ideas

Re: [AOLSERVER] POST file upload using multipart/form-data in C

2005-07-02 Thread Jim Davidson
On Jul 1, 2005, at 4:59 PM, Fred Cox wrote: --- Jim Davidson [EMAIL PROTECTED] wrote: Fred, Yup -- there are a few places in the code where there's a Tcl API without a corresponding C API. And, the docs are out of date, especially in the C API. Happily the code is generally readable

Re: [AOLSERVER] POST file upload using multipart/form-data in C

2005-07-01 Thread Jim Davidson
Fred, Yup -- there are a few places in the code where there's a Tcl API without a corresponding C API. And, the docs are out of date, especially in the C API. Happily the code is generally readable although that's a crappy answer to the poor docs. Anyway, in this case we'd need a few things:

Re: [AOLSERVER] New features in the next version of AOLServer

2005-06-28 Thread Jim Davidson
On Jun 28, 2005, at 11:01 AM, Dossy Shiobara wrote: On 2005.06.28, Bas Scheffers [EMAIL PROTECTED] wrote: I have never use ns_cache before, but it seems to me there is no way to store something in the cache from Tcl, is that the case? Would it be possible to implement? See the stand-alone

Re: [AOLSERVER] New features in the next version of AOLServer

2005-06-27 Thread Jim Davidson
Hi, The cache is actually a bit complex to follow -- I'll add some comments to help describe. Basically: -- Each thread maintains a cache of ADP code which includes per- interp byte codes and pointers to text regions in a shared area. When all threads no longer point to the shared text, it's

Re: [AOLSERVER] Problem building 4.0.10 on FC4

2005-06-27 Thread Jim Davidson
Odd -- I caught this error just last night and fixed. I'll checkin later today or tomorrow. I think it's a more strict warning for gcc4.0 -- the code has technically worked for years :) -jim On Jun 26, 2005, at 8:46 PM, Janine Sisk wrote: I started out with this error: conn.c: In

Re: [AOLSERVER] Problem building 4.0.10 on FC4

2005-06-27 Thread Jim Davidson
Ah -- sorry -- didn't read that far. As for the second error, the problem is the _np in pthread_kill_other_threads_np which means non-portable. It's an old API in LinuxThreads to kill all threads in the process-based threads which pre-date modern Linux kernels. The fix is to simply remove the

Re: [AOLSERVER] New features in the next version of AOLServer

2005-06-26 Thread Jim Davidson
Yup -- agreed, default has to be no-caching to be backwards compatible. I think that's how the code works -- at least that was my goal but I could have screwed it up :) I'll take a look. -Jim On Jun 25, 2005, at 10:20 PM, Dossy Shiobara wrote: On 2005.06.25, Jim Davidson [EMAIL PROTECTED

Re: [AOLSERVER] New features in the next version of AOLServer

2005-06-25 Thread Jim Davidson
Hi, We should put a page on aolserver.com with some details. We've moved the version to 4.5 from 4.1 to reflect the scope of changes. Scanning the ChangeLog and from what I can recall: * New connection management features including the ns_limits and ns_pools commands: -- ns_limits: control #

Re: [AOLSERVER] Ns_ConnReadLine return codes

2005-06-19 Thread Jim Davidson
In a message dated 6/19/05 5:51:32 AM, [EMAIL PROTECTED] writes: My reason for the 'maxline' usage is to cut off strange kiddies e.g., ones that try to exploit ms-iis bugs on any server. Ah -- then check for maxline in driver.c. I found the following config: if (!Ns_ConfigGetInt(path,

Re: [AOLSERVER] PHP works, but content-length is zero

2005-06-18 Thread Jim Davidson
In a message dated 6/18/05 11:35:09 AM, [EMAIL PROTECTED] writes: I'm playing around with the php module (libphp5.so). Using a browser, I get nothing displayed, so I telnetted in and I get the desired page, but the content length header is set to zero: HTTP/1.0 200 OK X-Powered-By: PHP/5.0.4

Re: [AOLSERVER] Ns_ConnReadLine return codes

2005-06-17 Thread Jim Davidson
In a message dated 6/11/05 2:17:01 PM, [EMAIL PROTECTED] writes: I can not find any 'return NS_OK' in nsd/connio.c::Ns_ConnReadLine. There are just two occurences of 'return NS_ERROR'. Is it so intentionally? Stupid bug -- I fixed it and checked it into the head version. Together with it,

Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Jim Davidson
Howdy, I've been following this thread the last few days -- great discussion. Let me add a few points and suggest how we can move forward. First, I'm responsible for the current approach of initializing Tcl interps in AOLserver and I agree with Zoran -- it's clumsy. Aside from failure on my

Re: [AOLSERVER] interpreter lifecycle

2005-05-28 Thread Jim Davidson
In a message dated 5/28/05 11:37:23 AM, [EMAIL PROTECTED] writes: 3. Use the package interface along with ns_ictl to manage state clearly, e.g., replace the confusing code in bin/init.tcl with the following and expect folks to own this config for their own install as they do with nsd.tcl:

Re: [AOLSERVER] Caching parsed ns_adp_parse -string results

2005-04-12 Thread Jim Davidson
In a message dated 4/12/05 10:06:54 AM, [EMAIL PROTECTED] writes: thanks for all your responses! I'm sorry I wasn't too clear about my problem. I don't want to cache the results of calling ns_adp_parse -string $my_string since parts of the result page contain request specific parts. What I

Re: [AOLSERVER] Leaky AS/Tcl memory allocator -- Tcl 8.4.7 the culprit

2005-04-07 Thread Jim Davidson
In a message dated 4/7/05 4:48:52 AM, [EMAIL PROTECTED] writes: This is the one. More precisely the unix/tclUnixThrd.c as of 8.4.7 (and later) looks like: void TclpFreeAllocCache(ptr)      void *ptr; {      extern void TclFreeAllocCache(void *);      TclFreeAllocCache(ptr);      /*       *

Re: [AOLSERVER] Leaky AS/Tcl memory allocator

2005-04-06 Thread Jim Davidson
In a message dated 4/6/05 1:44:46 PM, [EMAIL PROTECTED] writes: OK. Now, please, whoever wrote this "zippy" (whatever that means) can you please see what is going on? Or at least give me some hint where to start digging. I need to get rid of this "side effect" Hi, I wrote zippy and

Re: [AOLSERVER] Leaky AS/Tcl memory allocator

2005-04-06 Thread Jim Davidson
In a message dated 4/6/05 5:23:58 PM, [EMAIL PROTECTED] writes: Am 06.04.2005 um 22:31 schrieb Dossy Shiobara: Zoran, if you have some time, could you try building Tcl 8.4.0 with the threaded memory allocator and see if your tests show whether the same memory growth problem exists or not?

Re: [AOLSERVER] Google's perftools and TCMalloc

2005-04-01 Thread Jim Davidson
In a message dated 3/31/05 9:12:15 PM, [EMAIL PROTECTED] writes: But, (there's always a "but",) it appears that TCMalloc is a wholesale-retail allocator just like our Zippy (aka Tcl's threaded memory allocator).  In other words, it would seem that using TCMalloc won't offer us any performance

Re: [AOLSERVER] New Config API's which document default values.

2005-03-07 Thread Jim Davidson
In a message dated 3/6/05 11:08:33 AM, [EMAIL PROTECTED] writes: In my own experience reading AOLserver code, what I'd really wished for was more comments explaining WHY something was being done, as opposed to merely what or how.  (I suspect I've rambled on about this in the past...) Andrew

Re: [AOLSERVER] New Config API's which document default values.

2005-03-07 Thread Jim Davidson
In a message dated 3/7/05 11:33:52 AM, [EMAIL PROTECTED] writes: On Mon, Mar 07, 2005 at 12:38:58PM -0500, Andrew Piskorski wrote: On Mon, Mar 07, 2005 at 10:10:15AM -0500, Jim Davidson wrote: I'm thinking Tcl init and connection handling and garbage collection can be complicated

Re: [AOLSERVER] New Config API's which document default values.

2005-03-01 Thread Jim Davidson
In a message dated 3/1/05 7:52:22 PM, [EMAIL PROTECTED] writes: I had the timely fortune of needing to replace my crashed hard drive this weekend and I noticed a program being installed called 'indent'. Indent is a program which reformats the whitespace of C source code. Given a series of

Re: [AOLSERVER] Is AOLserver/Tcl 64-bit capable?

2005-01-31 Thread Jim Davidson
In a message dated 1/31/05 1:53:53 PM, [EMAIL PROTECTED] writes: I don't know how interesting this is to most folks, but I know it's important to a few of us.  To us, this is fantastic news, I think. Excellent! There are likely other aspects of AOLserver which may need to be updated to

[AOLSERVER] Re: [AOLSERVER] memory leak in 4.0.9?  (Long message.)

2005-01-15 Thread Jim Davidson
In a message dated 1/14/05 6:55:31 PM, [EMAIL PROTECTED] writes: Naive question: What if you just purposely crash AOLserver?  Will Valgrind tell you what you want then? There are probably known ways to make AOLserver crash just from Tcl, but it's especially easy if you're willing to write a

Re: [AOLSERVER] ns_adp_compress: apply gzip to outgoing ADP buffer

2005-01-10 Thread Jim Davidson
In a message dated 1/10/05 2:58:04 PM, [EMAIL PROTECTED] writes: But since the work is/will-be underway to make the adp's gzip savvy I thought why not making the built-in ns_return also? What about the original rl_returnz/ns_returnz modules being incorporated into the distribution? Hi,

Re: [AOLSERVER] ns_adp_compress: apply gzip to outgoing ADP buffer

2005-01-10 Thread Jim Davidson
In a message dated 1/10/05 3:27:42 PM, [EMAIL PROTECTED] writes: If try to use nsreturn [ns_gzip ...] the special handling for encodings won't be done correctly (that's my guess anyway, not having looked at the code).  You really need to do all the encoding jive before compressing. Yes --

Re: [AOLSERVER] Writing custom ADP Parsers

2004-12-16 Thread Jim Davidson
In a message dated 12/15/04 6:15:33 PM, [EMAIL PROTECTED] writes: I'm trying to build a restricted execution environment for ADP pages, and to make a clean break with the current code base, I want a new parser for ADP pages for some of my web pages. Poking through the AOLServer docs, I found

Re: [AOLSERVER] AOLSERVER Digest - 13 Aug 2004 to 14 Aug 2004 (#2004-174)

2004-08-16 Thread Jim Davidson
In a message dated 8/15/2004 1:25:36 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: BTW: It turns out the code to make this work, outside the various config junk, wasn't to complicated. Basically it required calling a function to collapse all the blocks together at the end

  1   2   >