fedserv/echo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Nest the ircd link under modules/protocol/

Browse source 
The protocol link is a different kind of module from the service
pseudo-clients, so give it its own home: modules/inspircd ->
modules/protocol/inspircd. A future ircd link is a new crate alongside
it. Workspace member, dependency path, the crate's own api path, and the
docs are updated to match. No code change.
This commit is contained in:
Jean Chevronnet 2026-07-14 14:28:18 +00:00
parent ad2a623120
commit a803177f8b
No known key found for this signature in database
5 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

7
MODULES.md
View file

@ -12,7 +12,7 @@ There are two kinds of module.
- A **protocol** (an ircd link like InspIRCd) implements `Protocol`.
Both live in their own crate under `modules/`. `modules/example/` is a complete,
minimal service to copy from; `modules/inspircd/` is the reference protocol.
minimal service to copy from; `modules/protocol/inspircd/` is the reference protocol.
## A service, end to end
@ -107,8 +107,9 @@ ignored.
A protocol crate implements `Protocol`: it turns raw server-to-server lines into
the normalized `NetEvent`s the engine understands, and turns the engine's
`NetAction`s back into raw lines. The engine never sees a raw line, so supporting
another ircd is one new crate — see `modules/inspircd/`. Wire it in `src/main.rs` where
`InspIrcd` is constructed.
another ircd is one new crate under `modules/protocol/` — see
`modules/protocol/inspircd/`. Wire it in `src/main.rs` where `InspIrcd` is
constructed.
## What the SDK deliberately does not give you