Proposal for changes in InformationBroker plugin about jspf HOT 3 CLOSED

Thanks for your suggestions. You are perfectly right, the InformationBroker 
right now is only for demo 
purposes, and for me to have a look if it's useful or not (and to see how a 
good and balanced IB interface 
should look like).

The idea of IB is to have a common place to register values, query them and 
listen for changes to these values.

The reason why subscribe fires even very early is that you can just subscribe 
to one channel and you get 
notified even of the initial value, the current behavior is intentional, but an 
option could be added not to get 
the initial result. 

ALL_SET might very likely be wrong, but I haven't verified that yet. However, I 
even thought about dumping 
the conditions completely and focussing only on single keys. 

Any suggestions about that?

Hi,
If your real-life project should be notified of already set items then an 
option is a
good solution. It's your code, at least :)

As of dumping multiple keys conditions, then it's natural to drop them in IB as 
such
logic can be moved inside those plugins that require complex behavior.

Also, I suppose your code fires listeners in separate thread, right? Probably, 
this
should be optioned too, as I met some cases when an item is quite complex (e.g. 
GUI
window), and it changes in parallel with plugin receiving and processing such
notification.

Hope this was useful for you.

InformationBroker has been completely revamped. The interface differs, it also 
replaces the Bus, and has a convenience InformationBrokerUtils helper class.