Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support broker-less P2P communication in Runtime API #31

Open
harrycodawang opened this issue Jan 23, 2019 · 0 comments
Open

Support broker-less P2P communication in Runtime API #31

harrycodawang opened this issue Jan 23, 2019 · 0 comments

Comments

@harrycodawang
Copy link

Besides Producer/Broker/Consumer topology, the Message/Stream communication use case could also apply to broker-less P2P communication. Basically, for the P2P communication, we could identify 4 communication styles:
Type 1. Oneway message/stream
Type 2. Request/Response
Type 3. Request/Stream
Type 4. Duplex stream
Currently the OpenMessaging API put pub/sub should be also able to support Type 1 P2P communication.
One possible way to enhance is to extend the interface SendResult

public interface SendResult {
    /**
     * The unique message id related to the {@code SendResult} instance.
     *
     * @return the message id.
     */
    String messageId();
}

For example, include a response in the RequestResponseSendResult, include a PeerTopic for the RequestStreamSendResult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant