Store objects in the room dag instead of the media repository? #1

New issue

Closed

opened 2018-06-09 14:11:13 +00:00 by jcgruenhage · 1 comment

jcgruenhage commented

2018-06-09 14:11:13 +00:00

Owner

No description provided.

jcgruenhage added the

Bikeshedding

label 2018-06-09 14:11:16 +00:00

jcgruenhage commented

2018-06-09 17:08:12 +00:00

Author

Owner

Pro:

We don't need to worry about servers going offline anymore, because cloning the repo would completely backfill the history.
We get better access control, because event access is authenticated already and has different access levels

Contra:

Performance would be horrible. While http GET'ting 7 million files is bad, getting that many events and parsing their json would be worse. Also, it's not only horrible for the client, inserting all those events and serving them to clients would be horrible.
Forks. This is the major reason why to go to the media repository instead of the room dag. Forking a repository with the objects being in the media repository just means pushing the refs to a new room, the actual object don't need to be copied. with them being in the room dag, you need to insert all of them again.

### Pro: - We don't need to worry about servers going offline anymore, because cloning the repo would completely backfill the history. - We get better access control, because event access is authenticated already and has different access levels ### Contra: - Performance would be horrible. While http GET'ting 7 million files is bad, getting that many events and parsing their json would be worse. Also, it's not only horrible for the client, inserting all those events and serving them to clients would be horrible. - ***Forks***. This is the major reason why to go to the media repository instead of the room dag. Forking a repository with the objects being in the media repository just means pushing the refs to a new room, the actual object don't need to be copied. with them being in the room dag, you need to insert all of them again.

jcgruenhage closed this issue

2018-06-09 17:08:12 +00:00

jcgruenhage removed the

Bikeshedding

label 2018-06-09 17:13:20 +00:00

No labels

Bikeshedding

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jcgruenhage/git-on-matrix#1

No description provided.