> This is extremely silly. The logger and the interfaces are both highly > modular and pluggable. If you want a logger that outputs the log in a > structured format to a file, a socket, a pipe or whatever, all you need > to do is ask. It's a two hour job.
Sorry? How does that work. It's *surely* easier for me to add some code to freenet.exe that actually tests the actual FNP port and port 8888 to see if they're actually working, than it is for you (or anyone else) to add specific logging code to fred AND for me to add some code to freenet.exe that reads and parses from the logfile/pipe/whatever. For the following simple reasons: 1. If we're logging to some kind of a file, detecting new logged messages will require writing code that reads from that log file, line by line, from the end, backwards. f**k that. Plus if anyone ever does add a trimming method to the existing logfile (as it currently grows without bounds, another of my pet hates), we lose the guarantee that a message is going to be in there anyway. 2. I can't immediately think of any adequate log message format or conduit that deals with the following scenarios. Fred was running, but has now died for unexpected reasons (e.g. jvm crash, process kill). No log message has been detected by the bunnyapp, it assumes everything is still running. User gets confused because bunnyapp says "yeh, rock and roll", but no pr0n appears on their browser. 3. We've had the situation in the past when it was clear from the logfile that everything *should* be working but it was also clear that everything *wasn't* working. It turned out to be a windows application issue, nothing to do with fred. So whatever fred might do to tell us that it's working, it may not be the case as far as end user applications go. 4. The only sane way to test if something is working is to *test if something is working*. Call me paranoid but if I told you your water supply hadn't been poisoned despite news reports to the contrary, but I hadn't actually checked the water myself, I'd only had a telephone conversation with the water company, wouldn't you be a little sceptical occasionally? 5. Logging, schmogging. Logging can be turned off. Freenet is fully functional without any logging. (And if not, why not?) 6. Only one person has to make changes to the code. You're a busy man. d _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
