[MGNLREST-126] Investigate: Return binary as base64 encoded, performance caused for client side Created: 11/Oct/17 Updated: 23/Oct/17 Resolved: 20/Oct/17 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Sang Ngo Huu | Assignee: | Dai Ha |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 1.5h | ||
| Time Spent: | 1d 2.5h | ||
| Original Estimate: | 1.5d | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | REST Queries |
| Sprint: | Saigon 118 |
| Story Points: | 3 |
| Description |
|
When listing dam workspace, binaries will be return as base64 encoded. It is too heavy for client side. We need to find other solution to serve binary |
| Comments |
| Comment by Christopher Zimmermann [ 16/Oct/17 ] |
|
This is a serious problem. Requesting assets could attempt to return a 50MB response. I think by default no binaries should be returned in REST requests. Typically, a link should be returned instead. A workaround in some cases is to set the depth parameter such that no binary is returned. But this will cause problems in some cases where you want things at the same depth of the binaries. |
| Comment by Mikaël Geljić [ 20/Oct/17 ] |
|