| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
correctly. Also defined a static const called
<tao_specific_message_types> which will tell how many TAO specific
message types we have. These TAO specific types will have negative
values in the enum type.
|
| |
|
|
|
|
|
| |
solved the problem I had earlier regarding not able to make more than
one invocation on the server.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
<Wait_On_Reactor> to work.
|
| |
|
|
|
|
| |
state of the incoming message.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Asynchronous).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Integrated all of Carlos' suggestions on to the architecture. First
tried to get the "Wait_On_Read" strategy to work. Not complete yet.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|