faq

Table of Contents

• Table of Contents
• About this page
• FAQ itself
  • Why OsMoSes?
  • What advantages has OsMoSes over JADE's built in mobility services?
  • Can I use some containers with OsMoSes and some with JADE's built in mobility services?

About this page

You know what a FAQ is!

FAQ itself

Why OsMoSes?

The main benefits given by OsMoSes are:

1. It allows you to save bandwidth by only transmitting the bundles necessary to define the agent migrating. If in the destination container there are enough bundles to define the agent, only its data is transmitted.
2. It helps you to assure consistency by ensuring the agent will be defined by exactly the bundles you expect it to be.
3. It ease deployment. You don't need to configure the agents classes in the classpath because, once the bundles have been transmitted (through migration), it will be automatically available every time you restart JADE (you "pay the cost" only once).

What advantages has OsMoSes over JADE's built in mobility services?

For the main advantages associated to OsMoSes are enumerated in the Why OsMoSes question.

In addition you can check the metrics results.

Can I use some containers with OsMoSes and some with JADE's built in mobility services?

OsMoSes is designed to be seamlessly integrated with JADE as a replacement for its built-in mobility service. However some changes in its interface do exists (mostly because some functionality defined in the default mobility service loose sense with the approach followed by OsMoSes) so incompatibilities may exist.
However, it is valid to use containers with OsMoSes and others without it in the same platform, but you will not be able to migrate agents between them. This is like this by design because, if OsMoSes allowed to migrate agents not defined as bundles, it could lead to odd and hard to debug behaviors in the platform.