Discussion: Moving the type definitions into its own crate

[AhegaoBurger]

Is your feature request related to a problem? Please describe.
So I am working on a PR for Zed to integrate the rmcp sdk in order to replace their existing custom MCP implementation and one of the engineers from Zed asks if they could just use the types instead of pulling the entire dependancy tree, which sounds reasonable to me so I decided to see if I could make it happen

Describe the solution you'd like
I created a separate rmcp-types crate with minimal dependencies so that if someone wants to just use the upstream type definitions they can do that just that (apparently that's how the Zed team works with DAP and LSP protocols)

Describe alternatives you've considered
I didn't really consider alternatives besides moving the types into its own separate crate, I'm not an expert in Rust so there very well could be a better way of doing this than my implementation, would love to discuss alternatives and options

Additional context
This idea of moving types into their separate crate with minimal dependencies seems sound, especially if that's how DAP and LSP are implemented and are being used by organisations building clients that integrate them so I would imagine it be sensible for MCP implementation in Rust to also follow a similar pattern

[jokemanfire]

It like ECS structure , split all the struct to component in a single crate?

[AhegaoBurger]

Sorry, not sure what you mean @jokemanfire, the point would be split the current two crates into at least three by adding a types specific crate

[jokemanfire]

Like split the crates/rmcp/src/model.rs to a new crate, I quite agree with it. :)

[AhegaoBurger]

Yeah, more or less, I have a first version done on my own branch, I haven't opened a PR since the guidelines are that I need to have a discussion with the maintainers/community about it