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

Initial support for XEP-0446: File Metadata Element #448

Merged
merged 1 commit into from
Dec 16, 2023

Conversation

vanitasvitae
Copy link
Member

Solves SMACK-894

XEP-0446: File Metadata Element defines a generic extension element format that can be used to describe file metadata.
This PR adds initial support for this protocol by implementing the element and provider classes.

private final Date date;
private final String dimensions;
private final Map<String, String> descriptions = new ConcurrentHashMap<>();
private final Map<HashManager.ALGORITHM, HashElement> hashElements = new ConcurrentHashMap<>();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above: This should not need to use ConcurrentHashMap.

Furthermore, don't we have support for XEP-0300 in Smack? If so, then there should be a Class for the <hash xmlns='urn:xmpp:hashes:2'/> element. If not, then we should add such a Class and use it there.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand this comment. HashElement is already from Smacks XEP-0300 implementation.

Copy link
Member

@Flowdalic Flowdalic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to address the comments, squashing and rebasing.

Also adds initial support for XEP-0264: Jingle Content Thumbnails

Solves SMACK-894
@Flowdalic Flowdalic merged commit 3d6fa5d into igniterealtime:master Dec 16, 2023
3 checks passed
@Flowdalic
Copy link
Member

Thanks, please see also my follow-up commit b5180f8

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.

2 participants