https://github.com/mtrnord/matrix_capnproto_fed

What if Matrix was written using Cap'n'proto and a RPC federation API?
https://github.com/mtrnord/matrix_capnproto_fed

Last synced: about 21 hours ago
JSON representation

What if Matrix was written using Cap'n'proto and a RPC federation API?

• Host: GitHub
• URL: https://github.com/mtrnord/matrix_capnproto_fed
• Owner: MTRNord
• License: apache-2.0
• Created: 2024-03-14T11:44:49.000Z (11 months ago)
• Default Branch: main
• Last Pushed: 2024-03-16T22:11:43.000Z (10 months ago)
• Last Synced: 2024-11-25T02:05:05.809Z (2 months ago)
• Language: Go
• Size: 121 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# What if Matrix was written using Cap'n'proto and a RPC federation API?

This question is what I am trying to proof by actually implementing this into synapse.

For simplicity this repo includes some go demo code for some of the details but

it also provides a suggested structure of folders for the proto files.

## Will there be an MSC?

Maybe but my hopes are either way very low that this will get mainline.

## Will there be a synapse PR?

Yes this is a major goal of this. It will also support fallback by design to the HTTP API

if the rpc API is not available.

## Will this work with $Loadbalancer?

It depends. Its doing RPC over unix or tcp sockets. So if your loadbalancer can handle that

it should work.

## Will this be faster?

Maybe. This is to be tested. However there exists some evidence that it might be faster than json

by at least up to 20x 

## What will be signed?

The message that holds the signature map will be signed in its canonical binary form.