Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Fixed
Priority: High
Fix Version/s: Engineering tracked issues, 2013.05, 5.2-alpha1
Affects Version/s: 5.1
Component/s: Content (images, XML, PDF, RSS, etc.), Platform > REST API v2
Labels:
None

Sprint:
Aconcagua Sprint 1

Description

Image variants need to be exposed via REST. However, for multiple reasons, they can't be exposed directly from a vnd.ez.api.Content response.

The main problem is that doing so would imply iterating over every alias for every image in the content, and generate the alias before outputing its URI. In terms of performances, this just won't work.

The first step is to provide specifications towards a solution.

Attachments

Issue Links

discovered while testing

EZP-20769 REST v2: Reading object containing ezimage datatype returns hardcoded ( and wrong ) results

Closed

relates to

EZP-23719 Missing contentType, width, height and fileSize properties in to the output of the load image variation REST response

Closed

EZP-22017 Missing API to load an image variation

Closed

links to

Pull request #371

Specifications

mentioned in: Wiki Page Loading...

(1 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Bertrand Dunogier

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 07/May/13 4:05 PM

Updated:: 02/Dec/14 10:34 AM

Resolved:: 12/Jul/13 5:40 PM

Time Tracking

Estimated:

Remaining:

Logged:

2d 6h 39m