On Tue, 2008-08-19 at 12:24 +1000, russell muetzelfeldt wrote:
> On 19/08/2008, at 11:59 AM, Tom Jackson wrote:
> > On Tue, 2008-08-19 at 11:37 +1000, russell muetzelfeldt wrote:
> >> On 19/08/2008, at 10:56 AM, Tom Jackson wrote:
> >>
> >>> You want a transactional database but you are using a filesystem.
> >>> Grow up.
> >>
> >> and
> >>
> >>> If your application wasn't the responsible party which violated the
> >>> expectation you state, I would agree (maybe).
> >>
> >> please go and re-read this thread, and get your parties straight.
> >
> > Sorry, I don't follow.
> ok, I'll spell it out.
> it's not my application that's violated the expectation I state. you  
> haven't been paying attention to the From: headers, and seem to have  
> mistaken me for the original poster of this thread.

Ah, okay. I didn't mean to point to any particular application, by "your" I 
didn't mean any particular you or your. 

> all I've been saying is that "ns_returnfile <filename>" returning the  
> content of something other than <filename>, contrary to the  
> documentation and common sense, is a bug. given that fastpath exists  
> for a (good) reason, and that the behaviour which triggers the bug is  
> marginal anyway, the correct response is "the bug will not be fixed,  
> here's why, and here's how to work around it".

It is an interesting point. But it isn't a bug. The purpose of the API
is to return a static file, not one which changes in under a second. It
is not a bug to not support code which is guaranteed to be slower than
common alternatives. 

Fastpath is designed to support return of smallish static content. It
isn't some ancient way of speeding up stuff that was slow, it was for
speeding up stuff that was already fast but was easy to make even

If you want to avoid use of fastpath, just set the configuration lower
than your dynamic content:

# Fastpath
ns_section "ns/server/${server}/fastpath"
ns_param cache                [set cache 10] ;# max entries ??
ns_param cachemaxsize         [set cachemaxsize [expr 5 * 1024 * 1024]]
ns_param cachemaxentry        [expr round(floor($cachemaxsize/$cache))]

Or, if the dynamic content is very small, or customized, don't write it
to a file in the first place. In general you are probably doing
something wrong if you write small content to a file and immediately
delete it. You are also likely doing something wrong if you are caching
large files.

tom jackson

AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to