lorenzodonini

Hey and thanks for the contribution. Just to understand the requirement better: are the current debug logs on ocpp-j level not enough? Incoming/outgoing raw messages are already being logged there.

I'm not sure I understand the issue at hand: `idTag` is being passed correctly to the request (although it's not necessary to override it again in the variadic function). Where...

@xBlaz3kx would you like creating a PR for the security extension? It's been on my ToDo list but didn't get to it yet. Happy to include it and then write...

@xBlaz3kx thanks a lot for opening the PR. I'll have a detailed look in the next few days. Regarding the structure, since the security extension is backported from v2, it's...

Concurrent request/response order cannot currently be guaranteed (especially on CSMS endpoints), since they run on two separate goroutines. Hence your follow-up request could indeed reach its destination before the response...

More details are needed, such as the exact setup and parameters being passed to curl. A simple websocket upgrade via curl example works just fine: ``` curl -v --include \...

@ysaakpr you can definitely do that on a networking level, but it won't solve the fact that you need to implement both v1.6 and v2.0.1 callbacks in your code. Btw...

Hello, I just tested this and it didn't throw any validation errors at all: ```go func test(chargePointID string) { cProfile := types.ChargingProfile{} cProfile.ChargingProfileId = 1 cProfile.StackLevel = 0 cProfile.ChargingProfilePurpose =...

> but is there a way to cancel the outstanding request? Not right now. I am planning to support passing a context for every request, which will allow you to...

FYI my explanation holds only for client implementations. Servers drop the state as soon as a client is disconnected, invoking the respective error callbacks.