aboutsummaryrefslogtreecommitdiff
path: root/369/index.md
diff options
context:
space:
mode:
Diffstat (limited to '369/index.md')
-rw-r--r--369/index.md50
1 files changed, 50 insertions, 0 deletions
diff --git a/369/index.md b/369/index.md
new file mode 100644
index 0000000..74423ea
--- /dev/null
+++ b/369/index.md
@@ -0,0 +1,50 @@
+Title: Add logging of DPI commands from server
+Author: acmiyaguchi
+Created: Tue, 18 Mar 2025 04:08:05 +0000
+State: closed
+
+I'm looking at dpid to get a sense of what it's doing. There's not a whole ton of documentation about the protocol. I've added a few logging macros and put them into the right places to better see the messages flowing in and out of the service:
+
+```
+$ ./dpid
+[dpid]: get_file_type: Unknown file type for style.css
+[dpid]: get_file_type: Unknown file type for style.css
+[dpid]: a_Misc_mksecret: e38f370d
+[dpid]: SEND - 5020 e38f370d
+
+dpid started (found 10 dpis)
+[dpid]: RECV - <cmd='auth' msg='e38f370d' '>
+[dpid]: RECV - <cmd='register_all' '>
+[dpid]: get_file_type: Unknown file type for style.css
+[dpid]: get_file_type: Unknown file type for style.css
+[dpid]: RECV - <cmd='auth' msg='e38f370d' '>
+[dpid]: RECV - <cmd='DpiBye' '>
+```
+
+These are the logs generated by startup, followed by `./dpidc register` and `dpidc stop`. There's a stray newline in there because most of the dpi messages are sent without newlines, while the generated port/secret are written using the same write macro with a new line.
+
+Here's a few more from browsing:
+
+```
+[dpid]: RECV - <cmd='check_server' msg='bookmarks' '>
+[dpid]: SEND - <cmd='send_data' msg='5030' '>
+[dpid]: RECV - <cmd='check_server' msg='proto.rdrview' '>
+[dpid]: SEND - <cmd='send_data' msg='5021' '>
+```
+
+
+--%--
+From: rodarima
+Date: Wed, 19 Mar 2025 22:40:05 +0000
+
+> There's not a whole ton of documentation about the protocol.
+
+This should be solved by extending the docs, not pulluting the stderr with protocol messages.
+
+--%--
+From: acmiyaguchi
+Date: Wed, 19 Mar 2025 23:50:53 +0000
+
+That's fair, I'll just keep this patch around for myself as I poke around.
+
+I'm curious about the protocol, but maybe it's better that I go build an extension to see how it works from the outside. \ No newline at end of file