Differences

This shows you the differences between two versions of the page.

--- pawsd:transports [2026/02/07 20:06] – created winter
+++ pawsd:transports [2026/04/07 17:06] (current) – winter
@@ Line 1: / Line 1: @@
 ====== Transports ======
-As noted at [[Protocol]], PawSD can operate over any underlying transport that can provide a request-response model. Some of them are described here.
+As noted at [[Protocol]], PawSD can operate over any underlying transport that can provide a request-response model. Some of them are described here. Note that as the protocol itself **does not** provide any data integrity, it's highly recommended to use a transport that does, such as TLS (but not TCP as data could be maliciously tampered with in transit).
@@ Line 12: / Line 12: @@
   - server reads the request, sends the entire response as-is, then closes the connection from their end
   - client reads the response, then closes the connection
+<WRAP center round todo>
+i'm considering, maybe this should be changed so that you don't have to close the connection at the end, and therefore you can reuse an open connection to send further requests? (like http keepalive)
+i'm not sure on this yet though
+</WRAP>
+For plain TCP, the suggested port number is 10016, and for TLS, 16123. But you can use any port you want :)