2 Replies Latest reply on Nov 21, 2007 11:44 PM by Trustin Lee

    One-way messages in Remoting 3

    David Lloyd Master

      I've been thinking about what Trustin said when we met a number of weeks ago, about one-way messages, delivery guarantee, and how it is implemented.

      Trustin's point back then was that a one-way message is actually very similar to a Request. It is simply a Request with no return value, or a return value that is ignored.

      Using Requests one can simulate all the desirable delivery guarantee levels. The "fire and forget" model can be done by doing an asynchronous send and just ignoring the returned FutureReply. Delivery guarantee can be done by using a synchronous invocation, and having the remote service just return the reply immediately (before processing the message). And a guaranteed completion can be done just by doing a regular request (but with no reply value).

      So I'm thinking that these interfaces should be unified. It will cut down on code and simplify the implementation of services as well.

      Thoughts?