Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
Proposal to allow frames to pass small amounts of application defined state to the frame server. (4kb, same as a browser cookie). Will be working on this one this week! (cc @df, inspired in part by framesJS passing data in frame URLs) https://warpcast.notion.site/Frames-State-Public-f3de69c1d12944e583a37204c98d25d9
13 replies
9 recasts
112 reactions
vrypan |--o--|
@vrypan.eth
Here is my concern: The state is sent from the server to the client, so that the client sends it back to the server. So, the server could save the state and just pass a sessionId (which is much simpler for the client). But if this is the case, the sessionId is easy to embed in a URL, so why? :-)
2 replies
0 recast
2 reactions
vrypan |--o--|
@vrypan.eth
Do we want to have clients do a job that servers could do (probably better)?
1 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
I started on this side (just use a server side session keyed by FID), but app developers clearly want to pass state: more than one advanced frame used URL query params to serialize state between frames. It does mean for many simple cases Frames don't need a session store.
0 reply
0 recast
1 reaction
