Thread: IRC-type logger with files based on three values

I'm starting to write an app that is similar to an IRC logger. Each log file will be based on three values or so -- user name, IP, and channel. The reason I have both user name and IP is so that I can keep track of what user names an IP uses or vice versa. I need the channel so the bot will be in multiple channels. I may add more values for each unique log file in the future.

For example, there will be 2 log files generated for user Foo, IP 123.123.123.123, channel 123 and for Foo, IP 123.123.123.123, channel 234.

What is an efficient way to generate a log file for each of these values? I thought about this for a while and all I can think of is to create a text file with three columns (one for each value) and every time the user talks, I check this text file and put their conversation in the appropriate log file. This requires file access every talk though, so it is not scalable.

Alternatively, I could just log everything in a single file and have another C app that splits up the conversation based on these three values. I'd like to implement both and see how major of a performance difference this is, but if you have more efficient ways, I'd love any feedback.

I was thinking about doing a static table in memory, but I don't know the number of entries. I could have 10, or I could have 9999. Should I instead use a dynamically allocated table?

Why not open/create/close text files based on user WHOIS information? Such as:

[email protected]
[email protected]

I imagine a dynamic table, used in any number of active channels, would get extremely large in a short period of time, and a static table insufficient. Also keep in mind that an IP address may not always be available, depending on server settings and user modes.

Originally Posted by kpreston

Why not open/create/close text files based on user WHOIS information? Such as:

[email protected]
[email protected]

I imagine a dynamic table, used in any number of active channels, would get extremely large in a short period of time, and a static table insufficient. Also keep in mind that an IP address may not always be available, depending on server settings and user modes.

Hmm that takes care of two the values...and getting the third is very easy. Thanks for the idea! I was thinking of coding practices and overlooked what IRC has already done for me!