muc: consider making handling messages easier #245
Labels
No Label
bug
CI
documentation
duplicate
enhancement
good first issue
help wanted
i18n
invalid
needs-investigation
ops
proposal
proposal-accepted
proposal-declined
question
refactor
security
testing
upstream
wontfix
Kind: Breaking
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Maintenance
Kind: Question
Kind: Security
Kind: Testing
Priority: Critical
Priority: High
Priority: Low
Priority: Medium
Reviewed: Confirmed
Reviewed: Duplicate
Reviewed: Invalid
Status: Blocked
Status: Completed
Status: Help wanted
Status: In progress
Status: Needs feedback
Status: Stale
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mellium/xmpp#245
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Right now when handling MUC messages we're requiring that the user create their own handler and have it check if a message is to an address that's also an open MUC channel. Eg. they have to register something like this on the muc and do a lot of work:
Instead, we should investigate other design possibilities. One that should be investigated is whether or not it's possible to have a
muc.MessageHandler
or similar that gets added to themuc.Client
and if non-nilmuc.HandleClient
will handle registering a handler that calls the message handler, passing in the matching channel. Eg. something like this:A more detailed proposal should be written up, or more discussion should probably happen before this is implemented.