Message Passing Tutorial: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content deleted Content added
Created page with "It's always a problem to decide if you use asynchronous or synchronous message passing. In this article I'll show you have both. I'll use a pseudo-code to describe the algorit..." |
mNo edit summary |
||
| Line 1: | Line 1: | ||
It's always a problem to decide if you use asynchronous or synchronous message passing. In this article I'll show you have both. I'll use a pseudo-code to describe the algorithm, so you can implement it to your language environment. Note that I refer sender and receiver as processes, it can be easily adopted to threads. |
It's always a problem to decide if you use asynchronous or synchronous message passing. In this article I'll show you how to have both. I'll use a pseudo-code to describe the algorithm, so you can implement it to your language environment. Note that I refer sender and receiver as processes, it can be easily adopted to threads. |
||
== Definitions == |
== Definitions == |
||
You should have a structure to be sent to another thread. I'll refer this as the message, and I assume you have these fields: |
You should have a structure to be sent to another thread. I'll refer this as the message, and I assume you have these fields: |
||