Complete.Org: Mailing Lists: Archives: gopher: January 2002:
[gopher] Re: Bucktooth+
Home

[gopher] Re: Bucktooth+

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Bucktooth+
From: Cameron Kaiser <spectre@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 16 Jan 2002 21:53:41 -0800 (PST)
Reply-to: gopher@xxxxxxxxxxxx

> It wasn't that difficult, but I still needed over 120 new lines of code,
> nearly doubling the size of buckd (now distinguished for my own purposes
> as buckd+

Might be interesting to look at.

> Cameron: you made it so that in the selector everything after a ? is
> counted as data and sent to the script like search input.  This seems to
> be what you use for dbrowse, but I did not see it in the protocol specs
> so it is no longer supported.  Do you want to put this into the
> protocol?  How should it merge with the other data sent, or should we
> just assume that these exclude each other.  I also apologize for messing
> up some of your pretty code.

It's not part of the protocol, just one of Bucktooth's features. Note
however that I'm wringing some subtle bugs out of the argument parsing
and these are due for -pr4. So this is by no means finalised.

I chose ? to do it since it seemed rarely used as part of a selector and
that it would be easily visually parsed since most HTTP GET-based CGIs accept
arguments the same way.

> What is a good way to check when a file has been last modified (ie for
> the admin block).  Keep in mind that this is being done in perl.

You could use the stat() call. One of the list elements returned is
the modification time; see the perlfunc manpage.

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@xxxxxxxxxxxxxxxxxxxx
-- There is no Dark Side of the Moon, really. Matter of fact, it's all dark. --


[Prev in Thread] Current Thread [Next in Thread]