capture dimse output

[geezer78]

I would like to be able to capture the dimse output in my code.
currently its being sent to stdout which could be captured of course but makes it messy.
I would prefer getting the output as an object with the results.

it would be great if that could be added.

[knopkem]

Indeed, this would be a nice improvement. The dimse output is currently produced by dcmtk via their internal logger, but this logger can be replaced. I will have a look at it.

[knopkem]

I tried adding a logforwarder that sends the captured logs to the js land. It did work to some extend but then crashed under heavy logging, so postponed this for now, but will try to find out a solution. Seems like the issue is rather with node-addon-api than dcmtk. Anyway, the latest version was changed to log dcmtk output to a rolling file called dicom.log in order to not slowdown the service.

[geezer78]

Wow, thanks for this and the update of dcmtk! I will check it out asap. Kind regards, Gijs

…

________________________________ From: Michael Knopke ***@***.***> Sent: Tuesday, January 30, 2024 1:04:34 PM To: knopkem/dicom-dimse-native ***@***.***> Cc: Geezer78 ***@***.***>; Author ***@***.***> Subject: Re: [knopkem/dicom-dimse-native] capture dimse output (Issue #63) I tried adding a logforwarder that sends the captured logs to the js land. It did work to some extend but then crashed under heavy logging, so postponed this for now, but will try to find out a solution. Seems like the issue is rather with node-addon-api than dcmtk. Anyway, the latest version was changed to log dcmtk output to a rolling file called dicom.log in order to not slowdown the service. — Reply to this email directly, view it on GitHub<#63 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABZIAAV5TYLE7HAOLGEEJILYRDOVFAVCNFSM6AAAAAA7UGCSACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJWGY4TMNBZGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>