Small changes in Assignment 2 (step-by-step)

[mthmulders]

Three minor textual changes:

• All other "Step" headers were at H2, only this one at H3
• I believe the text referred to the wrong application: it read FineCollectionService, but that's the application where the students are working on, while the context suggested it should read VehicleRegistrationService
• dapr deserves a uppercase D ;-)

[EdwinVW]

Thanks for these changes @mthmulders.

• I believe the text referred to the wrong application: it read FineCollectionService, but that's the application where the students are working on, while the context suggested it should read VehicleRegistrationService

This should read "FineCollectionService" actually. You specify the values for how the FineCollectionService calls the VehicleRegistrationService. And these are:

• 3601 : the port of the FineCollectionService's sidecar and
• VehicleRegistrationService : the app-id of the service that should be called

[mthmulders]

Thanks for these changes @mthmulders.

• I believe the text referred to the wrong application: it read FineCollectionService, but that's the application where the students are working on, while the context suggested it should read VehicleRegistrationService

This should read "FineCollectionService" actually. You specify the values for how the FineCollectionService calls the VehicleRegistrationService. [...]:

What I understood (after a lot of studying and re-reading) is that the text refers to the configuration of the FineCollectionService as far as it describes the interaction with the VehicleRegistrationService. I think the difference is in how the both of us interpret "values for the XXX" - to you, XXX is the application who owns that value, whereas I understood it as "the target of XXX", or in other words "the location where the application that owns the value can find their XXX". Let me just say that it got me completely on the wrong track initially... ;-)

How about this?

You can substitute the placeholders in this URL for the FineCollectionService with the appropriate values describing the location of the VehicleRegistrationService, this yields the following URL:

[EdwinVW]

What I understood (after a lot of studying and re-reading) is that the text refers to the configuration of the FineCollectionService as far as it describes the interaction with the VehicleRegistrationService. I think the difference is in how the both of us interpret "values for the XXX" - to you, XXX is the application who owns that value, whereas I understood it as "the target of XXX", or in other words "the location where the application that owns the value can find their XXX". Let me just say that it got me completely on the wrong track initially... ;-)

How about this?

You can substitute the placeholders in this URL for the FineCollectionService with the appropriate values describing the location of the VehicleRegistrationService, this yields the following URL:

I understand the confusion! But it is actually not the location of the VehicleRegistrationService (VRS) you specify. That is also the point I'm trying to make in the note after this text. You specify the app-id of the VHS and the Dapr http port of the FineCollectionService. Let's try this:

You can substitute the placeholders in this URL with the appropriate values so the FineCollectionService's sidecar can call the the VehicleRegistrationService, this yields the following URL:

Does that make more sense?

[mthmulders]

You specify the app-id of the VHS and the Dapr http port of the FineCollectionService.

Gotcha! The devil is - again - in the details.... I just didn't grasp that level of detail from the text. But the last suggestion works fine for me, I'll update the MR accordingly. Thanks for taking the time to consider it!

[EdwinVW]

Thanks for taking the time to consider it!

No problem. Thank you for challenging this!
The text should be clear. And if it's not, we should update it!