The cascade-api crate provides the basic serialization types for communicating with the daemon. But some important information about that communication -- namely, the HTTP paths to use for each kind of request, and the expected status codes returned -- are not embedded in cascade-api. The Cascade CLI and the daemon are manually kept in sync for these bits of information (although it hasn't been much of an issue, because they are rarely changed). It would be nice to embed this info in cascade-api so it is a complete standalone definition of our communication protocol.
The
cascade-apicrate provides the basic serialization types for communicating with the daemon. But some important information about that communication -- namely, the HTTP paths to use for each kind of request, and the expected status codes returned -- are not embedded incascade-api. The Cascade CLI and the daemon are manually kept in sync for these bits of information (although it hasn't been much of an issue, because they are rarely changed). It would be nice to embed this info incascade-apiso it is a complete standalone definition of our communication protocol.