This activity focuses on code production for holons. In the Janus platform, each holon is represented by a class. Janus offers two main kinds of holon: a threaded and a non-threaded one. The programmer has to choose the most appropriate one for the specific problem. Starting from the results of the Holarchy Design activity, the programmer chooses the most adapted version of Holon and can code the holon implementation by using the associated Janus primitives. When a non-threaded implementation is chosen, holon scheduling aspects have to be coded too. The three methods that govern the life-cycle of each holon have also to be defined (activate(), live(), end()); they are associated to the three main states of the holon’s life: activation, execution, and termination. As inspired by the Madkit synchronous engine, Janus provides a full set of tools to manage non-threaded holons execution.

This page was last modified on 29 July 2010, at 14:39. This page has been accessed 5,617 times.
Copyright 2010-2018 © IRTES Institute - UPR EA 7274 - Université de Technologie de Belfort-Montbéliard - Privacy policy