JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net
JPPF

The open source
grid computing
solution

 Home   About   Features   Download   Documentation   Forums 

.Net bridge limitations

From JPPF 6.0 Documentation

Jump to: navigation, search

Contents

Main Page > .Net Bridge > Limitations


1 No Java workloads for .Net clients

A JPPF job created from a .Net application cannot have Java tasks in it. This would require specific compilation and build features which are not currently available in the .Net bridge.

Please note, however, that you can still mix .Net and Java clients in the same JPPF grid, without limitation.

2 Tasks limitations

The following methods of the Task interface are not working for .Net tasks;

  • compute(JPPFCallable) : this method allows executing a callback on the client side from a task executing on a node
  • fireNotification(Objetct, bool) : enables the tasks to send notifications, either locally or via JMX. This method is not available for .Net tasks, however it is possible to listen to built-in task notifications that the JPPF nodes emit automatically.

3 No ClientListener and ClientConnectionStatusListener

The ability to receive notifications of new and failed client connections, along with the ability to receive status notifications for existing connections were not translated in the .Net Bridge. This implies that, from a .Net client application, you cannot be notified of events about new client connections or connection status changes.


Main Page > .Net Bridge > Limitations



JPPF Copyright © 2005-2017 JPPF.org Powered by MediaWiki