| August 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
| Jul Sep | ||||||
This site is no longer maintained.
My current weblog.
Monday, August 12, 2002What solutions exist for centralized searching of distributed web sites, "behind the firewall" ? I am specifically thinking about how centralized searching could be used to integrate multiple K-Log efforts within a single organization. The Google Search Appliance comes to mind, but it could be quite difficult to cost-justify without a larger KM effort and budget (GSA is $28k at the low-end).
MS Index Server is out because it doesn't have a crawler, and I haven't found anything promising on Sourceforge.
Radio Wish: Date / Time Formatting Options
Radio's date / time macros need to be configurable. For starters, the timestamps in my posts should be configurable to include the timezone and GMT offset. The Internet audience is global, it's natural to expect that many of my readers will be in another timezone and not be aware of which timezone my content was created in.
There are people who want 24-hour times, as discussed here and here.
Months ago, Ingo Rammer pointed out the issues of using Radio to publish an English-language web site from a German version of Windows.
Ideally, Radio would default to using the regional settings as specified by the OS. I don't mean "It's German windows, we'll use German day names." Windows has a "Regional and Language options" control panel that lets the user specify any language and use any format, and there are APIs to handle the dirty work (presumably Mac OS has something similar). Radio should respect those exact settings, and provide an easy way to override them.
TZ offsets are an acknowledgement of the global nature of the Internet. Most Internet RFCs require either offsets or that GMT be used whenever time data is exchanged.
