Shulou(Shulou.com)06/02 Report--

This article mainly explains "what are the common terms and commands of pomelo". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what are the common terms and commands of pomelo".

Schematic diagram of pomelo architecture

Terminology related terms explain gate-server gate, load balancing, do not participate in rpc, only clientPort, customer server sends request to gate first, gate assigns connector-serverconnect-server to client through hashing algorithm, and owns clientPort (j listens client connection) and port (provides service to backend), ① receives client connection request, creates connection with client, maintains client session ② receives client request to backend server. According to the routing strategy configured by the user, the request is sent to the specific back-end server ③ to receive the response of the back-end server to the client, and the message to the client is sent to the game-serve application logic server to complete the actual application logic. Provide services to client master-server to load configuration files, start server cluster, manage rpc inter-process communication for all servers, (1) namespace-sys: system rpc call (① backend server requests session ② backend server to front-end server to route user requests to backend server via channel to front-end server push messages ③ front-end server) (2) namespace-user: user-defined rpc Custom code and explicit rpc calls route to identify the location of a specific service or client push message ① for the server: the routing form is chat (server type). ChatHandler (a handler in the server). Send (a method in handler) ② for client: the routing form is onChatrouter, that is, after doing some operations based on the user session and the requested content Mapping it to a concrete application server idSession an abstract FrontendSession ① with a client connection can set the value of the settings field through FrontendSession, and then synchronize the value of the set settings to the original session by calling the push method of FrontendSession ② can also bind uid to session through the bind call of FrontendSession Of course, ③ can also access the read-only field of session through FrontendSession, but the modification to the same read-only field in FrontendSession as in session will not reflect that BackendSession is created and maintained by BackendSessionService in the original session. After the request is received by the back-end server, BackendSessionService creates the SessionService according to the parameters of the front-end server rpc to maintain all the original session information, including inaccessible fields. Bound uid and user-defined field BackendSessionService each method call to BackendSessionService will actually generate a remote call to Channel player id container request client request to serverresponseserver to return the notification sent by the client responsenotify client to the server, does not need the requestpush server to reply to the message actively pushed to the client, does not need the client to initiate requestfilter ① before: pre-processing (to determine whether the player has logged in or not Print statistical log, etc.) ② after: post-processing (releasing the request context, recording the total time spent on the request, etc.). The code that modifies the response cannot appear. Before entering the after, the response has been sent to the client handler which is located between before filter and after filter to implement specific business logic error handler global exception handling (can count error messages, organize exception response results) component has its own life cycle (such as start afterStart stop, etc.) The core function enables admin client to run its own process independently. It initiates a connection to master, and then manages the entire server farm by issuing requests or commands to master. Monitor runs in each application server. It registers itself with master and reports its server information to master. When the server farm changes, it receives the change message pushed by master and updates its server context master running in the application server. It collects information from the entire server farm and pushes changes to each monitor when there are changes At the same time, master also accepts requests from admin client and performs corresponding operations according to the commands issued by client, such as querying the status of the entire server farm and adding a server and other admin module-specific server monitoring and management module to realize the monitoring logic. There are four optional callback functions: ① masterHandler (agent,msg,cb) ② moniterHandler (agent,msg,cb) ③ clientHandler (agent,msg,cb) ④ start (cb) plugin A plugin is composed of multiple component and some event response handlers to flexibly extend the pomelo command-related command parameter details pomelo-V--version View pomelo version pomelo init [path]

Create a new project pomelo start-h--helpoutput usage informationpomelo start-e--env the used environmentpomelo start-D--daemonenable the daemon startpomelo start-d--directory The code directorypomelo start-t--type start server typepomelo start-i--id start server idpomelo list-h--helpoutput usage informationpomelo list-u--username administration user namepomelo list-p--password administration passwordpomelo list-h--host master server hostpomelo list-P--port master server portpomelo add-h--helpoutput usage informationpomelo add-u--username administration usern amepomelo add-p--password administration passwordpomelo add-h--host master server hostpomelo add-P--port master server porpomelo stop-h--helpoutput usage informationpomelo stop-Umuri- Username administration user namepomelo stop-p--password administration passwordpomelo stop-h--host master server hostpomelo stop-P--port master server portpomelo kill-h--helpoutput usage informationpomelo kill-u--username administration user namepomelo kill-p--password administration passwordpomelo kill-h--host master server hostpomelo kill-P--port master server portpomelo kill-f--forceusing this option would kill all the node processespomelo restart-h--helpoutput usage informationpomelo restart-u--username administration user namepomelo restart-p--password administration passwordpomelo restart-h--host master server Hostpomelo restart-P--port master server portpomelo restart-t--type start server typepomelo restart-i--id start server idpomelo master-h--helpoutput usage informationpomelo master-d--directory the code directory Thank you for your reading The above is the content of "what are the common terms and commands of pomelo". After the study of this article, I believe you have a deeper understanding of what are the common terms and commands of pomelo, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.