Package tigase.xmpp

Interface XMPPPreprocessorIfc

All Superinterfaces:
Comparable<XMPPImplIfc>, XMPPImplIfc
All Known Implementing Classes:
AbstractAuthPreprocessor, AddressingSanitizer, DomainFilter, InvisibleCommand, JabberIqAuth, JabberIqIq, JabberIqPrivacy, Message, MessageAmp, SaslAuth, StartTLS

public interface XMPPPreprocessorIfc extends XMPPImplIfc
Describe interface XMPPPreprocessorIfc here.
Created: Sat Oct 14 16:16:50 2006
Author:
Artur Hefczyc
  • Method Details

    • preProcess

      boolean preProcess(Packet packet, XMPPResourceConnection session, NonAuthUserRepository repo, Queue<Packet> results, Map<String,Object> settings)
      Performs pre-processing of packet. Intention for the pre-processors is to allow them for packet blocking.
      Parameters:
      packet - packet is which being processed. This parameter may never be null. Even though this is not immutable object it mustn't be altered. None of it's fields or attributes can be changed during processing.
      session - user session which keeps all the user session data and also gives an access to the user's repository data. It allows for storing information in a permanent storage or in memory only during the live of the online session. This parameter can be null if there is no online user session at the time of the packet processing.
      repo - this is a user data storage which is normally used when the user session (parameter above) is null. This is repository allows for a very restricted access only. It allows for storing some user private data (doesn't allow overwriting existing data) like messages for offline users and it also allows for reading user public data like VCard.
      results - this a collection with packets which have been generated as input packet processing results. Regardless a response to a user request is sent or the packet is forwarded to it's destination it is always required that a copy of the input packet is created and stored in the results queue.
      settings - this map keeps plugin specific settings loaded from the Tigase server configuration. In most cases it is unused, however if the plugin needs to access an external database that this is a way to pass database connection string to the plugin.
      Returns:
      the pre-processing result; if the value is ‘true’ then the packet is blocked and no further processing is performed.