I can activate SML tracing via kernel#SetTraceCommunications(true), but the SML messages don't seem to contain any client ID. The debugger is often a second client connecting to a kernel, and without client IDs on the messages it's not possible to tell the debugger SML calls apart from my own application's.
Do clients identify themselves somehow? Can I print out an ID somewhere? There is the SML Connection object, but the ID is just taken from the memory address (so it's not shared between client/kernel), and the name is always set to "unknown". I think we may need to extend SML a bit to properly specify a name; some random ascii would be fine. It just needs to be unique.
I can activate SML tracing via
kernel#SetTraceCommunications(true), but the SML messages don't seem to contain any client ID. The debugger is often a second client connecting to a kernel, and without client IDs on the messages it's not possible to tell the debugger SML calls apart from my own application's.Do clients identify themselves somehow? Can I print out an ID somewhere? There is the SML Connection object, but the ID is just taken from the memory address (so it's not shared between client/kernel), and the name is always set to "unknown". I think we may need to extend SML a bit to properly specify a name; some random ascii would be fine. It just needs to be unique.