[Embedlets-dev] Re: RoboCode...

[Andrzej J. T. <an...@ch...>]

Ted get's excited with his robot code:

> The main problem I have run into so far is that RoboCode limits each robot to
> only having 5 threads and this limit is hardwired into the code.  The RoboCode
> license expressly forbids decompiling or modifying the code so I am going to
> get on the RoboCode list tomorrow and ask if I can have written permission to
> up the number of robot threads for experimental purposes.

Keep in mind that the current Outpost container uses 7 threads by default:  
main thread, dispatcher thread and 5 event propagation threads.  However, 
these default values can be overriden using properties that the Event Manager 
reads on startup, so you could easily set the Event Manager to only use 3 
event propagation threads.

One of the beauties of Outpost for this kind of application is that the event-
based model means your application code (embedlets) are isolated from the 
having to know about threads, and you can modularize your code base by 
passing events around between components. For example:  Threat detection 
embedlet, Transport embedlet (movement), Attack embedlet, etc.

I hope to have some time in the evenings this week to start work on the XML 
configuration parsing for Outpost, to make it even easier to set up, add 
components, etc.

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com