You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be much easier to extract and use the JID's fields. More importantly, it would better enforce JID validity checking, which doesn't seem to happen now. For example, the XMPP Core RFC specifies that:
Each allowable portion of a JID (node identifier, domain identifier,
and resource identifier) MUST NOT be more than 1023 bytes in length,
resulting in a maximum total size (including the '@' and '/'
separators) of 3071 bytes.
If you're interested, I can give it a shot and submit a pull request.
The text was updated successfully, but these errors were encountered:
would this also enable using just the Name string for same-server messages instead of using full JID all the time? like.. "bob sends message to alice" instead of "bob@example.com sends to alice@example.com" if on the same domain!
JIDs are currently stored throughout the program as raw strings. If they were stored in a struct like this:
it would be much easier to extract and use the JID's fields. More importantly, it would better enforce JID validity checking, which doesn't seem to happen now. For example, the XMPP Core RFC specifies that:
If you're interested, I can give it a shot and submit a pull request.
The text was updated successfully, but these errors were encountered: