WCF data collection application using multi-threading and MEF interface definitions.

[jascam]

We want to rewrite an existing application suite which uses DCOM objects to a state of art .NET equivalent using the Windows Communication Foundation framework. This should lead to a more robust, manageable inter-program connectivity. By using threads on the data collection part we want to have the ability to (re)start/stop certain failing processes without effecting the other communications. To increase program module interoperability, we want to easily reconfigure the modules in use. We would like to achieve this without having to rebuild or even restart our main application and therefore think about using System.Composition (Managed Extensibility Framework) for the public interface layer(s). Data telegrams between participants contain (depending on the running logic) from a few floats to over 500 floats and strings, crossing the 1MB barrier and should be pushed a few times every second from data provider server to client(s) (WCF). Is this the right topology? How to accomplish the infrastructure layout as in addendum?

Attachments

AllInOne.pdf

Migrated CodePlex Work Item Details

CodePlex Work Item ID: '8850' Vote count: '5'

[jascam]

Sorry, I hit the entry key twice. Please all comment on the most recent issue number 8851 I guess...

Thx brraalgr.

This comment was posted by braalgr on 5/18/2011

[jascam]

This comment was posted by on 5/18/2011

[jascam]

This comment was posted by on 5/23/2011

[jascam]

This comment was posted by on 6/17/2011

[jascam]

This comment was posted by on 6/25/2011

[jascam]

This comment was posted by on 2/21/2013