The .Net and Android modules are no longer maintained or supported. They should be removed from the code base.

Currently we can do new Equal(...).not(). We propose to add a less cumbersome format such as new NotEqual(...)

Now that nodes can process multiple jobs concurrently, it seems the next logical step is to allow these jobs to come from any number of JPPF drivers. In particular, this will address the problem of the driver being a single point of failure more efficiently.

This will impact manay areas of the code, including:
* processing within the node (of course)
* handling of connection/disconnection events in the node (node connection strategy, when should a node reconnect)
* should we allow the driver connections to be prioritized, as in the client, and permit a failover hierarchy of drivers?
* grid topology monitoring: the topology will no longer be a tree. In particular, the nodes will have multiple drivers as parents, which is a significanty change in the monitoring object model
* how iwll it affect load-balancing?

JPPF 6.2 introduced the concept of dependencies between Tasks and also between Jobs. It would be nice if this feature could be expanded with Tasks/Jobs having access to the result-value of the tasks/jobs it depends on.