RE: 'Private' messages in Exodus

Understand. So what I would need to do to both peek at and trap packets would be as follows:
RegisterCallback(...
/special/message/x[@xmlns='http://pgmillard.com/jabber/foo.xsd'] 
(For packets I need to trap and don't want the core client to process.

RegisterCallback(...
/packet
(For packets I want be informed of)

This would work!!
-Fred

-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Peter Millard
Sent: Tuesday, February 03, 2004 2:37 PM
To: Exodus development
Subject: Re: [Exodus-dev] 'Private' messages in Exodus


Fred O'Leary wrote:
> Wouldn't it be easier, both for plugin developers as well as the core, to
> just implement the /pre option as follows:
> 1 ) All plugins that register for "pre" messages will get them.
> 2 ) If any of the plugin's return TRUE then the packet doesn't reach the
> core GUI

Not really :)

The current dispatching model ensures that the packet goes to all listeners for
that signal. Return values don't really exist. Adding the ability for a packet
to be "handled" would be a pretty significant refactoring effort.

pgm.

_______________________________________________
Exodus-dev mailing list
[email protected]
https://jabberstudio.org/mailman/listinfo/exodus-dev