The HTTP handlers in the components are split into reader and writer directories. This was a fairly arbitrary distinction, and turns out to not be so helpful. Most read APIs have a corresponding write API, and it is more natural for them to be in the same file rather than in different directories.

The prior naming was confusing, OutputRoomEvent consumed
OutputNewRoomEvents

* Implement filter POSTing and GETting.
Signed-off-by: NJan Christian Grünhage <jan.christian@gruenhage.xyz>

* Add missing '}' typo introduced during merge

* Still trying to fix that merge...

* Fix linting

Signed-off-by: NMTRNord <mtrnord1@gmail.com>

* Implement GET /rooms/{roomID}/state/{type}/{stateKey}

* Add comments

* Add config for setting up a jaeger opentracing reporter

* Remove redundant comment

* Add opentracing Spans to the HTTP APIs

* Add opentracing spans to the HTTP RPC clients

* Set the span in the request context

* More docstring

* Implement setting alias during room create

* Implement shared secret registration

* Use HexString from gomatrixserverlib

* Correctly check username validility

* Move prev event structure to component-wide types

* Renamed key for better understandability

* Implement /state endpoint

* Change rowsToEvents() to return an empty slice instead of nil in case of empty result set

* Doc

* Fix forgotten comma

* Specify HTTP method

* Update comment

* Remove debug fmt.Println

* Add table for storing invites in the syncapi

* Use the invite table to list the active invites for a user

* Update the invites table from the roomserver stream

* Include the invites table when determining the maxInviteID

* Add 'unused' lint

* Keep testdata consts

* Add errcheck linter

* Add config for 'fast' linters

* Fix errcheck lint stuff

* Fix errcheck lint

* Use a shared PostgreSQL sequence to generate ids.

Share an auto incrementing sequnce between the account data and
the room event table.
This means that account data updates can be received independantly of
room events updates.

This should give some basic support for fixing #212

* Remove redundant 'primary key'

* Re-number the SQL arguments

* Fewer lies in comments

* Use a read-only snapshot transaction for calculating sync responses

* gb vendor update github.com/lib/pq

* Make media repo use error rather than jsonErrorResponse

* Update comments

* gb vendor github.com/pkg/errors

* Fixup error formats

* Add contexts to device database

* Remove spurious whitespace