04-16-2010, 07:46 AM
Hi Admin,
As I mentioned in the related Modbus thread the Plugin part that polls the Modbus devices is a Windows Service and the communication between the Service and the ComfortClient is via Microsoft Message Queuing (MSMQ).
I designed it this way as MSMQ has some powerful networking features so I can scale-up and scale-out the design if the interest is there.
At the moment the Service and Client sit on the same PC as I\'ve used \"Private\" message queues (which impose this constraint). I did this to keep things simple while Ingo and I work out how the architecture develops and performs; really well at the moment by the way!.
That said I can switch to \"Public\" message queues very quickly with very few code changes and then you could split across multiple machines based on the standard architure for distributed MSMQ\'s. Not sure whether this is all managed by Active Directory etc as havent looked to closely yet, but anything is possible!
Why the question though?
Julian
As I mentioned in the related Modbus thread the Plugin part that polls the Modbus devices is a Windows Service and the communication between the Service and the ComfortClient is via Microsoft Message Queuing (MSMQ).
I designed it this way as MSMQ has some powerful networking features so I can scale-up and scale-out the design if the interest is there.
At the moment the Service and Client sit on the same PC as I\'ve used \"Private\" message queues (which impose this constraint). I did this to keep things simple while Ingo and I work out how the architecture develops and performs; really well at the moment by the way!.
That said I can switch to \"Public\" message queues very quickly with very few code changes and then you could split across multiple machines based on the standard architure for distributed MSMQ\'s. Not sure whether this is all managed by Active Directory etc as havent looked to closely yet, but anything is possible!
Why the question though?
Julian