Move response bodies out of DB

[gschier]

Why

Since Insomnia uses an in-memory database, large response bodies caused big problems.

1. Responses needed to be kept in memory always (leading to high RAM usage)
2. Had no way of loading response details from DB without retrieving the body too
3. Caused NeDB to crash when response DB totaled more than NodeJS's 256MB string size limit.

Details

• Remove Response.body and Response.encoding (old way of storage)
• Add new Response.bodyPath field that points the the location on the FS where the body is stored
• Compress/decompress response bodies before writing/reading to/from FS
• Add migration to migrate old way to new way
• Add test for migration

[JurrianFahner]

It was a nice feature... Is it possible to bring it back as a feature, so I can enable it in the preferences?
For example a checkbox somewhere with a warning?

[gschier]

Hi @JurrianFahner,

I'm not sure I understand what you want. This change should not be noticeable to the user, it just changes how responses are stored in the app. Can you elaborate on what you're asking for?

[JurrianFahner]

In that case I didn't understand change... If the change is not noticeable to the user, then you can ignore my comment.