1f349/dendrite
4
0
Fork 0
mirror of https://github.com/1f349/dendrite.git synced 2025-04-02 18:25:04 +01:00
Code Issues Packages Projects Releases Wiki Activity
dendrite/clientapi
History
Sam Wedgwood 9b5be6b9c5
[pseudoIDs] More pseudo ID fixes - Part 2 (#3181) 
Fixes include:
- Translating state keys that contain user IDs to their respective room
keys for both querying and sending state events
- **NOTE**: there may be design discussion needed on what should happen
when sender keys cannot be found for users
- A simple fix for kicking guests from rooms properly
- Logic for boundary history visibilities was slightly off (I'm
surprised this only manifested in pseudo ID room versions)

Signed-off-by: `Sam Wedgwood <sam@wedgwood.dev>`
2023-08-24 16:43:51 +01:00
..
api
feat: admin APIs for token authenticated registration (#3101)
2023-06-22 16:37:21 +00:00
auth
Move MakeJoin logic to GMSL (#3081)
2023-05-17 00:33:27 +00:00
httputil
Move MakeJoin logic to GMSL (#3081)
2023-05-17 00:33:27 +00:00
producers
refactor: update GMSL (#3058)
2023-04-19 15:50:33 +01:00
routing
[pseudoIDs] More pseudo ID fixes - Part 2 (#3181)
2023-08-24 16:43:51 +01:00
threepid
Use *spec.SenderID for QuerySenderIDForUser (#3164)
2023-08-02 11:12:14 +01:00
userutil
refactor: update GMSL (#3058)
2023-04-19 15:50:33 +01:00
admin_test.go
de-MSC-ifying space summaries (MSC2946) (#3134)
2023-07-20 15:06:05 +01:00
clientapi_test.go
Add config key for default room version (#3171)
2023-08-08 14:20:05 +01:00
clientapi.go
Move fedclient interface over to gmsl (#3061)
2023-04-24 16:23:25 +00:00
README.md
use go module for dependencies (#594)
2019-05-21 21:56:55 +01:00

README.md

This component roughly corresponds to "Client Room Send" and "Client Sync" on the WIRING diagram. This component produces multiple binaries.

Internals

  • HTTP routing is done using gorilla/mux and the routing paths are in the routing package.

Writers

  • Each HTTP "write operation" (/createRoom, /rooms/$room_id/send/$type, etc) is contained entirely to a single file in the writers package.
  • This file contains the request and response struct definitions, as well as a Validate() bool function to validate incoming requests.
  • The entry point for each write operation is a stand-alone function as this makes testing easier. All dependencies should be injected into this function, including server keys/name, etc.