Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider the capabilities of other clients and server #23

Open
nesium opened this issue Aug 18, 2023 · 1 comment
Open

Consider the capabilities of other clients and server #23

nesium opened this issue Aug 18, 2023 · 1 comment

Comments

@nesium
Copy link
Contributor

nesium commented Aug 18, 2023

We should of course consider the actual capabilities of other clients/servers. Ideally we'd simply fall back to optional values. So e.g if a Prose SDK consumer requests UserMetadata, local_time and last_activity are already optional but currently both IQs are sent regardless of the receiver's caps.

@nesium
Copy link
Contributor Author

nesium commented Feb 20, 2024

This also affects communication with the server, the server's MUC service and HTTP upload service. We'll need access to the stream properties in both xmpp-rs and strophe.js

@nesium nesium changed the title Consider the capabilities of other clients Consider the capabilities of other clients and server Feb 22, 2024
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

No branches or pull requests

1 participant