GitHub user spetz added a comment to the discussion: SDK crate split & new 
crate structue

The most important parts that come to my mind currently are:

- Move the shared data models (commands, responses, underlying data structures, 
client errors) to the new, lightweight shared SDK which could be referenced by 
both, server and existing Iggy SDK
- Cleanup the server errors, as some of them are part of the public SDK error 
enum type, while these are only used internally by the server

GitHub link: 
https://github.com/apache/iggy/discussions/1734#discussioncomment-13029108

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to