We are currently working on getting the last bits of the new SmartInspect release finished (which should be available at the end of February) and I decided to introduce another new feature of SmartInspect 2.0: the memory protocol.
The memory protocol can be used for writing logging information to memory instead of writing it directly to file or sending it to the Console. When needed, it can save its queue of logging data to a user-supplied stream or file. The memory protocol has been designed to allow exception reporting mechanisms to include a log file when an error occurs.
When an end-user sends an exception report to the developer, it is now possible to use rich SmartInspect log files in addition to traditional call stack information to inspect an error. And because the memory protocol can be configured to use only a tiny bit of memory space, it is both very fast and consumes only few resources and can stay enabled at all times.
We designed this feature especially to integrate SmartInspect better with exception reporting products like EurekaLog, MadExcept and similar solutions.
Customer Portal
New memory protocol in SmartInspect 2.0
We are currently working on getting the last bits of the new SmartInspect release finished (which should be available at the end of February) and I decided to introduce another new feature of SmartInspect 2.0: the memory protocol.
The memory protocol can be used for writing logging information to memory instead of writing it directly to file or sending it to the Console. When needed, it can save its queue of logging data to a user-supplied stream or file. The memory protocol has been designed to allow exception reporting mechanisms to include a log file when an error occurs.
When an end-user sends an exception report to the developer, it is now possible to use rich SmartInspect log files in addition to traditional call stack information to inspect an error. And because the memory protocol can be configured to use only a tiny bit of memory space, it is both very fast and consumes only few resources and can stay enabled at all times.
We designed this feature especially to integrate SmartInspect better with exception reporting products like EurekaLog, MadExcept and similar solutions.