|
|
|
|
desktop logging architecture?
Posted:
Mar 16, 2008 8:15 AM
|
|
|
Desktop apps can throw errors, some of which the remotely located developer would like to know about, for instance, if the error takes down the app !
Most programs now have the ability to pop up a little dialog and ask the end user if he/she wants to send an error notification to the author of the app.
My question is- is there an accepted best practice in terms of architecting this functionality? I've seen suggestions articles for everything from plugging into yahoo chat messenger to email to posting to a remote server. I am wondering 1) if anyone has ever lived with any of these suggestions for any length for time and what the pros and cons are and 2) is there a standard practices / best practices for implementing this 3) what is logged on the user's machine ? How much room do you allow to keeping a log on the user's machine? how do you read / send the log? etc. etc. just the basic things. I can program a solution, but I haven't done it before so I'm looking for other people's experience or ideas.
regards
|
|
java.net RSS
