Smart Client Logging to Central Server

Topics: CAB & Smart Client Software Factory
Nov 7, 2007 at 6:52 PM
I am on a team developing a Smart Client application for a customer and are trying to design a feature to support logging. We are leveraging Microsoft Best Practices wherever we can, and using Enterprise Library 3.1 and Smart Client Software Factory,

The client wants each of the clients to implement Store-And-Forward for logging. Essentially they want all the individual log entries for each of the clients to be stored locally and then forwarded to a central server that can be monitored by MOM. Have you or anyone you know done this? The client is unwilling to have MSMQ in the solution, although MQ Series may be a choice.

The customer is concerned about concurrency and locking issues when doing the forwarding of the log entries. Secondarily they are concerned with issues like filling up the log, or having a jumble of log entries from multiple clients making the log difficult to read. Any thoughts you have on this would be very helpful.

Nov 12, 2007 at 9:55 PM
I’m trying to see what advantage you gain by storing the log locally? Why can you not simply log all the transaction at the server end, as the calls are made and as a background process? What do you gain by storing locally first?

Storing on the server would resolve your concurrency and locking issues also!