[Versafix-users] VersaFix Update - 03052010 12:30 CST

[Russell E. C. <ru...@as...>]

Hi All,

The latest modifications to the VersaFix system have been committed. 
This includes some minor updates that touch most of the files and 
assemblies in the system. The most significant change is that several of 
the assemblies have been renamed to make them a little more consistent 
in terms of naming convention and use throughout the system. Specifically:

1. The Vfx.Metabase assembly is now Vfx.Settings.

The Vfx.Metabase assembly was named inappropriately at the start of the 
project, and we just got around to rectifying this. The new name is more 
appropriate, Vfx.Settings, since the classes defined in this assembly 
relate to managing configuration settings for a VersaFix application. 
The classes that were in Vfx.Metabase have also been renamed appropriately.

The Vfx.Settings assembly provides the IVfxSettings interface, which 
allows you to retrieve and assign configuration settings for components 
in the VersaFix system, as well as in your own application if you are 
building something using some of the VersaFix assemblies. The 
VfxAppSettings class in Vfx.Settings provides a concrete implementation 
of this interface, so you now do this:

IVfxSettings mySettings = new VfxAppSettings();

As opposed to doing this:

IVfxMetaSection mySettings = new VfxMetaSection();

2. The Vfx.ServiceContainer assembly is now Vfx.Services.

In the spirit of renaming the Vfx.Metabase assembly, we've also renamed 
the Vfx.ServiceContainer assembly to Vfx.Services. The components in 
that assembly have also been renamed, in the same fashion as was done 
with the Vfx.Metabase assembly, so you now do this:

IVfxServices services = new VfxAppServices();

As opposed to doing this:

IVfxServiceContainer services = new VfxServiceContainer();

These changes were just made so that all instances of classes that 
provide access to their settings and services do so in a more consistent 
fashion, for example:

IVfxSettings settings = MyObject.Settings;
IVfxServices services = MyObject.Services;

instead of the older, more inconsistent method of doing this:

IVfxMetaSection settings = MyObject.Settings;
IVfxServiceContainer services = MyObject.Services;

In addition, we've improved the event dispatching model for the FIX 
service implementations, and knocked out some minor defects in the IPC 
code and related modules.

As always, if you encounter any problems or have any concerned, please 
don't hesitate to contact me or any other member of the development team.

Thanks,

Russ

PS: There will be a lot of activity in the source tree over the next few 
days as we get closer to transitioning the project to BETA status.

-- 
Russell E. Curry
CEO
Assimilate Technology, Inc.
www.assimilate.com
715-928-2717 (mobile)