On Sun, Aug 16, 2009 at 22:39, Niklas Gustavsson<[email protected]> wrote: > On Sun, Aug 16, 2009 at 3:56 PM, Bernd Fondermann<[email protected]> > wrote: >> Sure. XMPP clients + servers support sending 'spontaneous' presence >> stanzas to jids which are not a contact (MUC rooms, for example). This >> is not handled by the server yet (see >> PresenceAvailabilityHandler.handleOutboundDirectedPresence). >> For a session, directed presences must be recorded and handled >> appropriately (see >> http://tools.ietf.org/html/draft-ietf-xmpp-3921bis-00#section-4.6 ). >> >> Otherwise, MUC won't work (so I set VYSPER-6 to be blocking MUC as you >> might have noticed). > > Let me change my mind again .-) > > Are you sure this really impacts the MUC module? Given it will get and > handle all messages sent for a subdomain, the normal presence handler > won't be involved (except for inbound stanzas for the users in the > room). I've now written some integration tests, and entering room, > exiting room and sending messages to the room seems to be working > against a running Vysper server. I will commit these tomorrow as I > need to catch some sleep now :-)
Yes, MUC is definitively effected. I'm not talking about the MUC code receiving a presence stanza from a client. (BTW, your use of "messages" is ambivalent. do you mean 'message stanza' or 'stanza' in general?) I'm talking about the server receiving a presence stanza from its client which is then to be routed to the server as a 'directed presence'. The server needs to take special care and keep track of directed presences. Everytime the presence get's an update, it must be propagated to the receivers of directed presence, including unavailable presences. This handling is not currently done in Vysper and since there is no federation possible with other servers, you will never be able to enter a MUC room with a 'regular client'. Bernd
