Race between stateSave and ssp requests

ericatkin

Hi,
I use server side processsing and the colvis part of the buttons extension. The server dynamically builds a query based on saved column visibility settings. Toggling a columns visibility appears to trigger a stateSave request and an ssp request concurrently, so sometimes the ssp request is processed on the server before the stateSave request, and therefore, the generated query doesn't include the newly visible column. This results in an empty column in datatables until the next draw is trigger by some other interaction. It seems to me that the colvis code should wait (when in stateSave mode) for the stateSave to complete before issuing a draw. Am I missing something?
Eric