From: Michael K. <mi...@ta...> - 2001-05-27 00:04:45
|
<snip> It helps occasionally > > troubleshoot problems we have with user errors ("I didn't make that purchase!" > > - well, the POST data from your IP at that time shows you did, etc.) Overkill > > for most apps, yes, but imposing these kinds of structures can really be > > helpful. Wow, maybe ASP had a redeeming quality? ;) > > yes, exactly. you can easily extend request to keep an _autitable_trail_ of > _every_single_thing_ever_ that comes into the app :) > > now, for joe bob's beer mart, this is probably not a big concern, for some > other people I know... yeah.. bigtime. > I think I'm posting twice - sorry. Using outlook, and I just ain't used to it! :( On another note - back in the day, we had a company come in to my office that was going to sell us log analysis software. They also had a hardware sniffer that would sniff and log ALL data to an SQL database (probably only MS at the time). Their big claim to fame at the time was that it logged POST data as well as GET stuff, and it'd sort it out into columns in a table, so you could query against it later. Breaking each GET/POST variable into a column might be overkill, but the idea had appeal. MINIMUM $25k, which sounded a lot at the time. It scaled per website on your network, which seemed a poor way of doing it - we had some sites with 50+ servers, and some shared on 1 server. Anyway, the crux is that having this capability in an app system is quite useful. We've got it in place, and as I said, for some sites, one in particular, it's great. Yeah, it can slow the servers down some a bit, but when you've got multiple servers in the first place, it ain't too bad. And certainly cheaper than a hardware sniffer. :) I certainly don't recall being able to do this in ASP, although I'm sure you *could*. Certainly wouldn't be as easy, imo, as PHP. Anyway, just saying good luck with the project. :) MK |