Why use separate service process?
• Centralized logging management. External tools can be used to configure the logging system, without worrying about correct serial ports and modules when writing your logging code. Except in rare situations like logging during boot when you cannot configure LogMan server manually before use. You can always do it programmatically from your application though. • Reducing risks associated with serial connections. • Reducing the size of your application. • Your code is faster. By using asynchronous sending, logging does not reduce the responsiveness of your applications as much, since you do not have to wait for the log sending to finish. • There are not enough serial ports available, if you want to test two or more applications/threads simultaneously. If the serial connection was handled in your application, you could have only 1 reliable connection. The connection can be shared, but I don’t know if that is reliable enough. With separate process, I don’t have to care.
Related Questions
- What happens if a candidate who is recruited from outside of the Public Service is invited to the matching process but does not receive an offer of employment?
- What's involved in the Verizon Fios Internet Service Installation process?
- Does a separate check have to be submitted for each Service of Process?
