Constants and comments

This commit is contained in:
Mark Haines 2017-06-27 14:51:29 +01:00
parent a620f30a02
commit f705480cf0
3 changed files with 13 additions and 9 deletions

View file

@ -159,7 +159,7 @@ func (t *txnReq) processEvent(e gomatrixserverlib.Event) error {
// TODO: Check that the event is allowed by its auth_events.
// pass the event to the roomserver
if err := t.producer.SendEvents([]gomatrixserverlib.Event{e}, ""); err != nil {
if err := t.producer.SendEvents([]gomatrixserverlib.Event{e}, api.DoNotSendToOtherServers); err != nil {
return err
}

View file

@ -40,6 +40,10 @@ const (
KindBackfill = 4
)
// DoNotSendToOtherServers tells us not to send the event to other matrix
// servers.
const DoNotSendToOtherServers = ""
// InputRoomEvent is a matrix room event to add to the room server database.
// TODO: Implement UnmarshalJSON/MarshalJSON in a way that does something sensible with the event JSON.
type InputRoomEvent struct {

View file

@ -70,14 +70,14 @@ type OutputRoomEvent struct {
// Or empty if this event shouldn't be pushed to other servers.
//
// This is used by the federation sender component. We need to tell it what
// event is needs to send because it can't tell on its own. Normally we
// if an event was created on this server then we are responsible for
// sending. However there are a couple of exceptions. The first is that
// when the server joins a remote room through another matrix server, it
// is the job of the other matrix server to send the event over federation.
// The second is the reverse of the first, that is when a remote server
// joins a room that we are in over federation using our server it is our
// responsibility to send the join event to other matrix server.
// event is needs to send because it can't tell on its own. Normally if an
// event was created on this server then we are responsible for sending it.
// However there are a couple of exceptions. The first is that when the
// server joins a remote room through another matrix server, it is the job
// of the other matrix server to send the event over federation. The second
// is the reverse of the first, that is when a remote server joins a room
// that we are in over federation using our server it is our responsibility
// to send the join event to other matrix servers.
//
// We encode the server name that the event should be sent using here to
// future proof the API for virtual hosting.