Content
@
0 reply
4 recasts
4 reactions
Varun Srinivasan
@v
Frame Redirect Design: Redirect vs Payload We're considering two different approaches for implementing the redirects. Devs, which do you prefer and why? https://warpcast.notion.site/Frame-Redirect-Response-vs-Payload-da2bb0e4212a4664ade8d38751e416f7?pvs=4
22 replies
22 recasts
90 reactions
bark bark
@king
Response strategy seems favorable. With payload there's no room for new features (considering the URL limit) in the future and there's not much control over the action by the Frame host. Response strategy offers both flexibility on the limits and the redirect signature can be handled by the frame.
2 replies
0 recast
0 reaction
Varun Srinivasan
@v
1. What control over the action is limited? In both cases you can send down a URL to send the user to, and nothing else. 2. What new features would be prevented by URL limit?
1 reply
0 recast
1 reaction
bark bark
@king
There wouldn't be any interaction on redirect between the user and the frame and in terms of the redirect feature, there's a limited space to fit in extra data (by both the frame and the client) on top of the redirect signature as you noted down on the URL limit of 2k bytes in case there's new data to be added in fu.
0 reply
0 recast
0 reaction
