I am receiving it correctly with my MessageFilter, and I would like to drop it. The main problem of further (or previous?) processing is that it appears a chat window (it is a heading packet but i guess it would happen also with normal) and I don’t want that.
I thought I could add a listener, then add a CustomizedFilter (not a simple MessageFilter), do whatever i want inside there and return accept->false if it matched my packets or accept->true so it can be processed by others. Does it make sense? And is there a way that my listener is the first (otherwise the windows appear before it’s dropped)?
I don’t understand what you mean with “CustomizedFilter” and “MessageFilter”. You are talking about rules in the PacketFilter plugin, right? All packets that are not of type IQ can be droped. Just choose “Drop” as action.
If you are talking about implementing your own PacketInterceptor, you maybe want to take a look on the Raptor plugin, which has much more features than PacketFilter. (however, its also much more complicated to use… )
Mh no, I was just searching for some problem similar to mine (I am developing a plugin for Spark, and custom headline Messages are sent by Openfire) and I found this thread.
Since the section is: Ignite Realtime > Plugins and Libraries > Packet Filter > Discussions
I thought I could find the best suggestion here for a library (being a Smack, Spark, or PluginFilter function I don’t care, even though I would prefer to avoid the plugin).
So, what I meant was:
I developed a Spark plugin which creates a MessageFilter (from Spark functions) and processes it.
The problem it that it is a headline Message, thus Spark listener open a window for it.