Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle Charge Point response #40

Open
gianmarcoodorizzi opened this issue Sep 24, 2021 · 1 comment
Open

Handle Charge Point response #40

gianmarcoodorizzi opened this issue Sep 24, 2021 · 1 comment

Comments

@gianmarcoodorizzi
Copy link

Hello,

as far as I managed to understand, the provided ExampleServerTestApp waits for incoming requests from a charge point (e.g.: a BootNotificationReq) and responds with a suitable response (a BootNotificationRes). These are all requests generated by the CS, while responses are generated by the CP.
What is missing, though, is the ability to handle responses from a charge point, e.g.: the central system sends a UnlockConnectorReq and it should accept and parse the received UnlockConnectorRes.
I've been trying to add this functionality, but I had no success. The fact that Scala is completely new to me is not helping.

Can someone be so kind to provide a hint on how to manage CP repsonses?

Thank you in advance.

@azolotko
Copy link
Contributor

azolotko commented Sep 25, 2021

These are all requests generated by the CS, while responses are generated by the CP.

It's vice versa. The function you return from handleConnection is supposed to handle requests coming from a CP to the CS.

What is missing, though, is the ability to handle responses from a charge point

In ExampleServerTestApp, you can actually see an example of how to send a request to a CP and handle a response from it.

conn.send(...) returns a Future of a response:

Schermafbeelding 2021-09-25 om 10 50 13

Are you familiar with Future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants