Difference between revisions of "Cattaskv2009 Communication"
| Line 27: | Line 27: | ||
+ Writing stable cross domain code is not an easy job. We had some annoying and strange remoting bugs with the current CatTaskService. | + Writing stable cross domain code is not an easy job. We had some annoying and strange remoting bugs with the current CatTaskService. | ||
| − | === MSMQ === | + | === MSMQ === |
| + | |||
| + | Firstly, | ||
Revision as of 12:00, 19 March 2009
Contents
Communication in Cattask v2009
What kind of communication do we need?
In the real production environment, because of the use of network balancing, one CatGlobe site is deployed in three separate servers. Besides, we decided that there will be one "Cattask" for one deployed instance of a site. The running production environment should look like:
The problem is that the three cattasks won't run independently. Instead, they must contact with each others to share information about scheduled tasks, tasks execution...
So what communication technology should we use?
We have investigated 3 communication techniques so far: remoting, WCF and MSMQ.
Remoting and WCF
Remoting and WCF are rather the same in term of how we send data from one CatTask to the another: CatTask01, for example, sends data *directly* to CatTask02 using known configured port. However, WCF is newer and easier to use than remoting.
- Pros:
+ We can sure that they meet our requirements, i.e. they can be used to develope the new CatTask.
- Cons:
+ Writing stable cross domain code is not an easy job. We had some annoying and strange remoting bugs with the current CatTaskService.
MSMQ
Firstly,
