中文

The framework doesn't depend on any third party components

• a master process and multiple subprocesses(worker processes)
  • the master process is responsible for signal processing
    • such as reviving the subprocess, log rotate (kill -USER1 master_pid) ...
  • the worker processes handle specific network requests (use epoll LT mode)
• configuration file and log system
• threads pool processing client messages
• a thread and message queues handle the sending of messages
• delay reclaiming connections in connection pool
• heartbeat packet mechanism and detection timer queue to reclain connections
• using specific message format to solve tcp packet sticking problem

By default, the source code is configured to http mode. If you need to configure tcp mode, please modify the variable of config.mk under the root path.

export USE_HTTP = false

• Implementation of tcp mode in subclass Mgx_logic_socket
• Implementation of http mode in subclass Mgx_http_socket

In addition, this project also implements a coroutine library, and implements a set of cosocket's APIs based on this coroutine library, but note that it's not integrated into above framework. You can see their use in the test directory.

Mainly realize code:

• coroutine
• coroutine schedule
• cosocket

Note: The coroutine library currently only implements x86-64 and ARM64 platforms

start in host machine

make -j4
./mgx
curl 127.0.0.1:8081  # or view web page in browser

start in docker

docker build -t mgx:latest .
docker run -itd -p 8081:8081 mgx:latest
curl 127.0.0.1:8081  # or view web page in browser

You can access https://127.0.0.1:8081 to view the web page in browser