In a multi-step workflow (like server actions), should the client send a growing list of data, or should the client send only the data that has been requested in the most recent step?
Current implementation is that the client only sends what's requested on each step, but, this ends up causing the back end to have to cache state for each request id, which, for most actions, is a lot of overhead and not necessary at all if the client sends the list of all data requested thus far.
Changing this should be a non-breaking change to the communication protocol / API. It's worth considering.
In a multi-step workflow (like server actions), should the client send a growing list of data, or should the client send only the data that has been requested in the most recent step?
Current implementation is that the client only sends what's requested on each step, but, this ends up causing the back end to have to cache state for each request id, which, for most actions, is a lot of overhead and not necessary at all if the client sends the list of all data requested thus far.
Changing this should be a non-breaking change to the communication protocol / API. It's worth considering.