Forwarding this note from Ed, regarding recent updates to VHMsg.

Just as a reminder, VHMsg is the VHuman communication library, currently 
built on Apache's ActiveMQ. SmartBody does not require VHMsg, and is not 
used by the Reykjavik PandaBLMR, but it does make it very easy to drive 
SmartBody and integrate your own tools and commonents. Expect to see a 
release of many of USC's internal tools before the end of the year, all 
of which depend on ActiveMQ and VHMsg.


Anm

-------- Original Message --------
Subject:        VHMsg library changes
From:   Edward Fast <[email protected]>



Hi All,

There have been a significant number of changes to the VHMsg, the 
library that handles ActiveMQ messages that all VHuman components use.

Probably the most important change is the environment variables used by 
the library have been renamed:

- ELVISH_SESSION_HOST is now VHMSG_SERVER

- ELVISH_SCOPE is now VHMSG_SCOPE

However, changes have been made so that these environment variables are 
entirely **optional**. For most users, you will **not** need to set 
these environment variables.

You will usually need to set these if you are working in a multiple 
machine environment (gunslinger saloon or VR Theater, for example), or 
if you have some setup where you are simultaneously testing multiple 
versions of the program (very rare).

For developers, please note that this functionality is now built-in to 
the VHMsg library. You no longer need to be retrieving environment 
variables in your code, or doing anything like that. Passing zero 
parameters to VHMsg at startup should be the default.

If your component is part of the normal VHuman build process, then I 
have already made changes to the libraries so that it builds and runs. 
If your component is **not** in the build process, you will need to make 
these changes if you want to use the latest version of the VHMsg 
libraries. This is also true if you maintain your source outside of our 
repositories (if we only have binaries). If you are unsure whether or 
not this is the case, ask me.

I have maintained compatibility with the underlying protocol, so 
existing binaries should continue to work fine (given previous 
requirements of env variables, etc).

If you know of others outside of this distribution list, please forward 
it on.

Here are the specific changes for each language implementation of VHMsg:

C++

- elqueue.lib has been renamed to vhmsg.lib

- tt_utils.lib is no longer a part of vhmsg. The tt_utils functionality 
has been moved into vhmsg proper (used to be elqueue)

- vhmsg.lib now has a dependency on pthreads

- ttu_open() now has optional parameters for server and scope. Most apps 
should not pass any parameters.

TCL

- ttSetScope has been removed (added an optional parameter to ttOpen)

- ttOpen has been changed so that server and scope are optional 
parameters. Most apps should call ttOpen like this: ‘ttOpen notices’ 
with no other parameters.

C#

- The output .dll has been renamed to vhmsg-net.dll.

- renamed the namespace to VHMsg

- renamed the main class to VHMsg::Client

- renamed the message class to VHMsg::Message

- added a polling option to the library so that messages can be received 
on the same thread.

Java

- the output .jar has been renamed to vhmsg-java.jar

- renamed the class package to edu.usc.ict.vhmsg

- renamed the main class to VHMsg (from ElvinUtility)

- added a polling option to the library so that messages can be received 
on the same thread.

- if you want to retrieve the values that VHMsg are using for server and 
scope, create the class, then call getServer() and getScope()

If you have specific questions, please feel free to ask me.

Thanks!

Ed


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Smartbody-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartbody-developer

Reply via email to