Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to realize the RPC authentication mode of SocketD protocol". In the daily operation, I believe that many people have doubts about how to realize the RPC authentication mode of SocketD protocol. The editor has consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "how to realize the RPC authentication mode of SocketD protocol". Next, please follow the editor to study!

SocketD is a binary point-to-point communication protocol and a new network communication layer 7 protocol. Designed to be used in distributed applications. In this sense, SocketD can be an alternative to other similar protocols such as RSocket. Its message protocol specification has the characteristics of asynchronism, two-way back pressure, multiplexing, disconnection reconnection, message-based and so on. Only Java implementation is provided for the time being, and it is currently used as the sockte channel protocol for Solon rpc.

In this case, the signature right is added to the RPC call mode as an example:

Interface definition

The Rpc mode borrows Nami as the client definition (Nami is a Solon companion framework and is positioned as a Rpc general client)

@ NamiClient ("demo:/demoe/rpc") public interface HelloService {@ Handshake boolean auth (String sn, String token); String hello (String name) } server / / launch server public class ServerApp {public static void main (String [] args) {/ / launch Solon container (SocketD bean&plugin is managed by solon container) Solon.start (ServerApp.class, args, app-> app.enableSocketD (true)) .socket ("*", (session) Message)-> {if (message.flag ()! = MessageFlag.handshake) {if (session.getHandshaked () = = false) {System.out.println ("this client is bad I want to send a contract without the right to sign: (") Session.close ();}); / / .socket (..) Instead of @ ServerEndpoint, use}} / / to define the remote service component @ Mapping (value = "/ demoe/rpc", method = MethodType.SOCKET) @ Component (remoting = true) public class HelloServiceImpl implements HelloService {@ Override public boolean auth (String sn, String token) {Session session = (Session) Context.current (). Request (); if ("1" .equals (token)) {session.setHandshaked (true) System.out.println ("sign successfully!"); return true;} else {session.setHandshaked (false); return false;}} public String hello (String name) {return "name=" + name }} client / / launch client public class ClientApp {public static void main (String [] args) throws Throwable {/ / launch Solon container (SocketD bean&plugin is managed by solon container) Solon.start (ClientApp.class, args); / / [client] calls [server] rpc / / HelloService rpc = SocketD.create ("tcp://localhost:28080", HelloService.class) If (rpc.auth ("1", "1")) {System.out.println ("RPC result:" + rpc.hello ("noear"));}} at this point, the study on "how to implement the RPC authentication mode of SocketD protocol" is over. I hope to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.