YegorKozlov commented on PR #11: URL: https://github.com/apache/sling-org-apache-sling-servlets-get/pull/11#issuecomment-1573452163
> What about changing the approach and you provide a link to the binary as part of the JSON instead of dumping its content within the JSON? @joerghoh that's actually how I ended up doing it for now :) My goal is to achieve symmetry between json export/import for the basic units of content in AEM like cq:Page, cq:Tag, etc. Since pages can contain images with inline data, those get lost and my idea was to transfer them as base64 in infinity.json. I'm not aiming at a universal json round-tripping which is hardly possible. I just wanted to make it more symmetric. So far I do N+1 GET requests to fetch the content, where N is the number of binary properties whose names start with a colon: - one GET to fetch infinity.json with the resource content - a GET to fetch each nt:file node with the binary data. So the idea was to fetch all the content in one go. @enapps-enorman I fully understand the memory consumption concern and it sounds serous enough to put this PR on hold. I'd like to see base64 in the json eventually, and I agree it should be streamed, not dumped. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
