You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While there isn't a clear use for this in the OCPP spec, it would nonetheless be useful for testing and other applications if a call can be made without expecting a response.
The call option could be something like {noReply: true}.
The call should resolve to undefined as soon as the RPC message is flushed to the client's open websocket.
If/when a response does arrive, it should be treated as a "bad message" and emit a 'badMessage' event.
The text was updated successfully, but these errors were encountered:
While there isn't a clear use for this in the OCPP spec, it would nonetheless be useful for testing and other applications if a call can be made without expecting a response.
The call option could be something like
{noReply: true}
.The call should resolve to
undefined
as soon as the RPC message is flushed to the client's open websocket.If/when a response does arrive, it should be treated as a "bad message" and emit a
'badMessage'
event.The text was updated successfully, but these errors were encountered: