Content
@
0 reply
4 recasts
4 reactions
Justin Hunter
@polluterofminds
Frame debugger that accurately tells you why your seemingly well-formed html doesn’t work. Someone ship it.
6 replies
0 recast
6 reactions
Tony D’Addeo
@deodad
what isn't working for? on my plate to make some improvements to it this weekend
2 replies
0 recast
1 reaction
kk
@king
Is there any chance of extending the post expiry duration to allow more complex executions?
1 reply
0 recast
1 reaction
Tony D’Addeo
@deodad
tldr right now, best bet is start computation on an initial message & deliver results on a subsequent one patterns are still being explored but for now 5s seems reasonable both for clients to hold open connections & from UX perspective see this thread for related discussion https://warpcast.com/gregfromstl/0x56ca8e12
1 reply
0 recast
1 reaction
kk
@king
I shared some thoughts about this. I thought it would be possible for the client to retry if the response code is other than 200, 302, & 503 to indicate progress. I’m guessing a queue is maintained by WC backend so request resource has a cost in any case.
1 reply
0 recast
2 reactions
Tony D’Addeo
@deodad
yea something like that could make sense keep sharing and exploring—frames are new and rapidly evolving, just a matter of balancing complexity and prioritization
1 reply
0 recast
0 reaction
kk
@king
Come to think of it that strategy is heavily reliant on the client whether to implement such polling mechanism and the client will always want the most efficient choice which is to not have it.
1 reply
0 recast
0 reaction
Tony D’Addeo
@deodad
I'd say clients optimize for UX over efficiency, just needs to be a reasonable design
0 reply
0 recast
0 reaction
