Feature/allow headers update

[shalom-aviv]

Example of changes for #99

[FZambia]

Hello @shalom-aviv

Thanks for opening PR and investigating the solution.

Could you please show how you are planning to use this in real code? What will be a trigger for headers update in practice? I generally understand the need in updating headers dynamically, but I am not sure yet what is the best approach for this. So some real-life code could help me to understand.

[shalom-aviv]

Hello @shalom-aviv

Thanks for opening PR and investigating the solution.

Could you please show how you are planning to use this in real code? What will be a trigger for headers update in practice? I generally understand the need in updating headers dynamically, but I am not sure yet what is the best approach for this. So some real-life code could help me to understand.

In my case, obtaining a new token can be done synchronously, so the changes in the this pull request were sufficient. Overall, I wanted to assess the feasibility and scope of changes required for parameter updates.

In a real scenario, obtaining a new token would be asynchronous. I've looked into how you handle JWT token updates and I think adding the ability to update connection settings in a similar manner would be a natural fit.

To be able to determine .upgradeError and obtain the actual status code from the server, I had to make WSError public, but this only applies to StarscreamWebSocket.

Check changes here: shalom-aviv#1