Azander has quit [Read error: Connection reset by peer]
Alanonzander has joined #spacedock
politas has quit [Ping timeout: 204 seconds]
<Endlessbit>
<morning
politas has joined #spacedock
* Thomas
wonders if he can count 4 am as morning
<Thomas>
hi
egg is now known as egg|zzz|egg
Alanonzander has quit [Remote host closed the connection]
Azander has joined #spacedock
<VITAS>
yes you can
<VITAS>
schrift-krassifikation :P
<VITAS>
oder krassinierung
<VITAS>
vollfettination
<VITAS>
over 850 spacelink downloads
politas has quit [Ping timeout: 200 seconds]
politas has joined #spacedock
dpbk has joined #spacedock
dpbk has left #spacedock [#spacedock]
<SpaceDock>
[OpenDock] StollD pushed 1 new commit to master: https://git.io/v7V28
<SpaceDock>
OpenDock/master e0d4605 Dorian Stoll: Prevent original events
egg|zzz|egg is now known as egg
aradapilot has quit [Ping timeout: 204 seconds]
politas has quit [Ping timeout: 204 seconds]
politas has joined #spacedock
aradapilot has joined #spacedock
aradapilot has quit [Remote host closed the connection]
aradapilot has joined #spacedock
<Thomas>
VITAS: RockyTV: Ok, so I got mod uploading to work. It is ugly as heck, because I encode the file as base64 and put it into the json request, but it works :D
<SpaceDock>
[OpenDock] StollD pushed 2 new commits to master: https://git.io/v7VQl
<Qboid>
* dorian: Encode and decode the zip file as base 64
<Qboid>
* dorian: Fix for permissions
<VITAS>
yes thats ugly :)
<VITAS>
what about multipart post?
<Thomas>
That would require a seperate route just for the file
<VITAS>
yes but isnt the site all about efficient file handeling? :)
<Thomas>
Because I dont think you can mix JSON and multipart, and I dont want to switch the whole route to multipart
<Thomas>
Well, the only difference between multipart and json file is that there is a bit json around the file. multipart would also just encode the file somehow in the request
<VITAS>
i cant judge how ineffiecient it is but imagine that dude uploading his city mod with over 600mb
<Thomas>
VITAS: I don't think it is less efficient than multipart.
<VITAS>
in that case: go ahead
<Thomas>
hmm, but there is one problem: allocation overflow
<VITAS>
like on large files?
<Thomas>
yes
<VITAS>
so you could imitate multipart
<VITAS>
buy chunking uploads
<Thomas>
So I am going to make a generic file upload route, and have stuff like update give out tokens for this route
<VITAS>
but is that realy less of a hussle than a seperate route?
<SpaceDock>
[SpaceDock-Backend] StollD pushed 1 new commit to master: https://git.io/v7VjK
<SpaceDock>
SpaceDock-Backend/master f16274d Dorian Stoll: Use a seperate route for uploading the file instead of base64
<Qboid>
Starting build #75 for job SpaceDock-Backend (previous build: SUCCESS)
<SpaceDock>
[OpenDock] StollD pushed 1 new commit to master: https://git.io/v7VjX
<SpaceDock>
OpenDock/master 84cb3b1 Dorian Stoll: Use a seperate route for uploading the file instead of base64