Yet another messaging system/architecture

[John Lokanis]

I finally completed version 1.0 of my messaging system (or messaging architecture if you prefer that nomenclature) and I figured I would post it here and see what mistakes other can find in my approach. 

My basic goal was to build something that could replace the old school messaging in my pre-LVOOP applications.  So, I wanted something that allowed for flat messaging (all processes are peers and can direct message each other) and had some type checking on the messages (I replaced the old typedef'd enum and variant with a message class).

I also wanted it to be easy to extend with additional features, such as a message log or the ability to send messages between application instances.

Along the way, I added a way of building hierarchical message systems like Actor Framework.

I also added subscriptions like JAMA.

And I tried out dynamic processes and well as static ones.

 

I am attaching a series of example projects, each one contains the core message architecture components so if you unzip them all, it will overwrite those parts each time.

 

The basic concept of the architecture is comprised of four components:

The system class defines the overall functionality of the message system

The message class that all messages inherit from

The transport class that defines the generic interface for sending and receiving messages

The process class that creates the message handler.  (This is roughly equivalent to an Actor in AF.)

 

The examples demonstrate remote messaging, dynamic processes, hierarchies of processes and message subscriptions.

Most basic example: Message System Basic Example.zip

Examples for demonstrating client-server network messaging:

Message System Client Example.zip

Message System Server Example.zip

Example of dynamically loaded processes: Message System Dynamic Process Example.zip

Example of a hierarchy of message systems (like AF): Message System Isolation Example.zip

Example of message subscriptions (like JAMA): Message System Subscription Example.zip

Please comment (good or bad) on the system overall and how it is organized.  I am sure there is lots of room for improvement.

Thanks for the feedback!

-John

 

ps. If you have any ideas for what to name it, let me know,  YAMS? (yet another message system) TUMS? (the ultimate message system  ) Any other ideas?