Philip Monk 68279d91e4 gall: remove message type from wire ... %leave over the network didn't work because we included the message type in the wire from gall, so the duct for the initial %watch and the %leave were different. We need to know the message type so we can route the acknowledgment as %poke-ack, %watch-ack, or no-op. This moves this piece of information to a piece of state, where we queue up the message types per [duct wire]. Ames guarantees that acknowledgments will come in order. This also includes an easy state adapter. The more interesting part of the upgrade is that we likely have outstanding subscriptions with the old wire format. The disadvantage of storing information in wires is that it can't be upgraded in +load. So, here we listen for updates on the old wire format, and when we get them we kill the old subscription, so that it will be recreated with the new wire format. As an aside, this is a good example of what we mean when we say subscriptions may be killed at any time, so apps must handle this case. Finally, this fixes the "attributing" ship to ~zod for agent requests. This information was ignored for agent requests, but including it causes spurious duct mismatches.		2019-12-10 19:32:26 +08:00
..
brass.pill	(re)release: v0.10.0	2019-12-05 02:25:00 +08:00
ivory.pill	release: v0.10.0.rc-1	2019-12-04 19:41:43 +08:00
solid.pill	gall: remove message type from wire	2019-12-10 19:32:26 +08:00