2016-05-12 04:36:12 +08:00
|
|
|
---
|
|
|
|
title: Design Concept
|
2016-05-26 01:54:28 +08:00
|
|
|
items:
|
|
|
|
- { type: file, name: memory-buffers.md }
|
|
|
|
- { type: file, name: event-handler.md }
|
|
|
|
- { type: file, name: events.md }
|
|
|
|
- { type: file, name: conn-flags.md }
|
2016-05-12 04:36:12 +08:00
|
|
|
---
|
|
|
|
|
|
|
|
Mongoose is a multi-protocol networking library that implements non-blocking,
|
2016-07-21 21:30:03 +08:00
|
|
|
asyncronous IO and provides event-based APIs. It has three basic data
|
2016-05-12 04:36:12 +08:00
|
|
|
structures:
|
|
|
|
|
|
|
|
- `struct mg_mgr` is an event manager that holds all active connections
|
|
|
|
- `struct mg_connection` describes a connection
|
|
|
|
- `struct mbuf` describes data buffer (received or sent data)
|
|
|
|
|
2016-07-21 21:30:03 +08:00
|
|
|
Connections could be either *listening*, *outbound* or *inbound*. Outbound
|
|
|
|
connections are created by the `mg_connect()` call. Listening connections are
|
|
|
|
created by the `mg_bind()` call. Inbound connections are those accepted by a
|
|
|
|
listening connection. Each connection is described by the `struct mg_connection`
|
2016-05-12 04:36:12 +08:00
|
|
|
structure, which has a number of fields like socket, event handler function,
|
2016-07-21 21:30:03 +08:00
|
|
|
send/receive buffer, flags, etc.
|
2016-05-12 04:36:12 +08:00
|
|
|
|
2016-07-21 21:30:03 +08:00
|
|
|
Mongoose's usage pattern is to declare and initialise event manager, create
|
2016-05-12 04:36:12 +08:00
|
|
|
connections and create an event loop by calling `mg_mgr_poll()` in a loop.
|
|
|
|
`mg_mgr_poll()` iterates over all sockets, accepts new connections, sends and
|
2016-07-21 21:30:03 +08:00
|
|
|
receives data, closes connections and calls event handler functions for the
|
2016-05-12 04:36:12 +08:00
|
|
|
respective events.
|