Skip to content

Conversation

@adiaholic
Copy link
Contributor

No description provided.

@vanitasvitae
Copy link
Member

vanitasvitae commented Sep 10, 2020

Nice! I see you are not yet fed up with Smack development 👍

I guess you are going in the right direction. I'd implement full ecaps2 first and then see how to unify ecaps2 and caps1 under a common API that ideally is not too different from caps1. Maybe you can "hide" ecaps2 and caps1 under the current caps1 API even, that would give you the benefits from ecaps2 while users can reuse the same API they are already used to.

@stokito
Copy link
Contributor

stokito commented Oct 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants