IRC channel logs
2024-07-20.log
back to list of logs
<kriskowal>what does spritely do for delimiting captp messages? <kriskowal>or rather: is the protocol merely a stream of sequential syrup structures, like a JSON stream? <kriskowal>(i’m sure it will surprise no-one that delimited JSON is not particularly well defined and varies wildly) <kriskowal>the question is interesting to me because of layer and coupling between the netlayer and captp layer. if the answer is syrup-over-netstring, then syrup is clearly in the captp layer and netstring is clearly in the netlayer. <kriskowal>but if it’s serial syrup values, there isn’t a clear boundary or the same flexibility. the netlayer has to be syrup aware, so it isn’t a matter of combing a generic transport/netlayer and a generic serialization/captp layer, but a cross product of these as they evolve. <kriskowal>so i’m advocating for syrup over netstring, but curious where we stand today <dthompson>kriskowal: it's a stream of sequential syrup structures, if I'm understanding you right. <kriskowal>this comes up because my mind wandered back to “what if i wrote a tiny go program that managed xs processes and multiplexed their io” <kriskowal>agoric runs a node/xs hybrid on a go supervisor and from time to time i get back to…“what if we only had _one_ js engine” <kriskowal>and also…what if the distributed system layer (endo) also leaned harder into XS <kriskowal>this is relevant only because the thing in common is delimited messages <kriskowal>and we currently delimit messages with netstring <dckc>ping? is this bridged to matrix? let's see...