Websocket log

💡 Describe the solution you’d like

I want to see websocket messages send from server and messages send from client (application)

🙋 Do you want to develop this feature yourself?

• Yes
• No If you provide some advice how add this feature or provide classes name to start analyzyng source code to add this feature.

[MiSikora]

It would be a hard task. Chucker uses interceptor API to inspect HTTP requests. Web sockets do not use this mechanism and the only thing you could do is to implement WebSocketListener and try to inspect messages. Though I say try because it is very complex task (might even not be feasible to make it properly ATM). Things to consider:

• Should there be a separate ChuckerWebSocketListener or make ChuckerInterceptor implement required interface.
• How to handle incoming messages? Text-based is easy. But recently, we added BodyDecoder interface to enable parsing of custom data by users, so we should think of support for binary–based messages.
• How to display this data in the UI? Same tab for HTTPS and WS traffic doesn’t seem IMO optimal.
• How to store data in the database? Currently it’s not that great to add new models. #259
• Should we support all WS events or only messages? Former is better but it complicates UI and data model.

[cortinico]

Given the current state of the library I’m not sure this is a straightforward thing to achieve, but would be interesting to know whether this is a direction the library would take, or whether I should explore something like this independantly.

I’m currently working on https://github.com/ChuckerTeam/chucker/issues/259 It will be possible to inject custom HTTP events inside Chucker in the future. I haven’t thought about making it a fully multi-purpose data module, but shouldn’t be that hard after we implement #259