Changes between Version 8 and Version 9 of VirtualHumanLoader


Ignore:
Timestamp:
08/07/12 23:54:18 (7 years ago)
Author:
dennisr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VirtualHumanLoader

    v8 v9  
    3434 
    3535__ActiveMQPipe __ 
    36 Module: org=HMI   name=HMIActiveMQPipe  
    37 Connects your realizer seamlessly to the ActiveMQ network, through the {{{asap.bml.request}}} and {{{asap.bml.feedback}}} channels. 
    38 No configuration settings; connects to ActiveMQ on localhost, default port. 
     36Module: org=HMI   name=!HMIActiveMQPipe  
     37Connects your realizer seamlessly to the !ActiveMQ network, through the {{{asap.bml.request}}} and {{{asap.bml.feedback}}} channels. 
     38No configuration settings; connects to !ActiveMQ on localhost, default port. 
    3939{{{ 
    4040<PipeLoader id="..." loader="hmi.activemq.bmlpipe.ActiveMQPipeLoader"/> 
     
    4242 
    4343== Rerouting of BML to Engines == 
    44 At the end of the file, you can override all default routings. Each type of Engine generally claims a default set of behaviors, but sometimes you want to send, e.g., face behaviors to a AsapPictureEngine instead of to the AsapFaceEngine, etcetera. 
     44At the end of the file, you can override all default routings. Each type of Engine generally claims a default set of behaviors, but sometimes you want to send, e.g., face behaviors to a !AsapPictureEngine instead of to the !AsapFaceEngine, etcetera. 
    4545 
    4646Each route consists of a fully qualified classname of the behavior, and the id of the engine that should be responsible for that behavior type.