Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
New frame feature: frames can now pass up to 4kb of state to the frame server! This makes it easier for frame devs to build simple, stateful, reactive apps. (Think React state in your frame). See the stateful counter frame below for an example: https://stateful-counter-frame.vercel.app
24 replies
22 recasts
397 reactions
Andrei O.
@andrei0x309
Having state was already possible on the server because the frame posts identification to the server. Nothing stops a server from maintaining and creating state in any kind of database or persistence/cache layer like Redis. This only makes things less expensive and easy on serverside but is not a new feature.
1 reply
0 recast
2 reactions
horsefacts
@horsefacts.eth
Yes, for lots of use cases you probably still want a backing store like Redis.
1 reply
0 recast
2 reactions
christopher
@christopher
this is how @cookie works. don’t think we ever shared this, but your cart is Redis cache.
1 reply
0 recast
2 reactions
Andrei O.
@andrei0x309
I guess many people have assumed that. Redis is the most common choice for having a state for a fc frame. And as @horsefacts.eth implied it will also provide more fine-grained control than having the state be maintained through post roundtrips. It's all a matter of your implementation needs.
0 reply
0 recast
1 reaction
