[MGNLREST-313] Introduce Stateless flag for REST personalization Created: 18/Jun/21  Updated: 13/Jul/21  Resolved: 13/Jul/21

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLPN-542 Get (stateful) personalized content f... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: Headless p13n
Sprint: HL & LD 31, HL & LD 32, HL & LD 33
Story Points: 0.5

 Description   

We need to introduce new flag in the endpoint definition in order to distinguish between stateful and stateless calls to the endpoint.

AC:

  • Introduce personalizationTraitMode setting with external / internal values in the JcrEndpointDefinition


 Comments   
Comment by Christopher Zimmermann [ 21/Jun/21 ]

Would a "stateless" flag ever apply to something besides p13n?
If its p13n specific, then maybe the name should reflect that... like "statelessPersonalization". Or "statefulPersonalization".

Comment by Jaroslav Simak [ 21/Jun/21 ]

It'll apply only to p13n, we should also clarify the naming - stateless / stateful and the default value.

Generated at Mon Feb 12 06:58:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.