Ecdar / Ecdar/Ecdar-Test

Use async queries instead of blocking

Open
#29 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Instead of having multiple instances of the engine and blocking them, we should send queries asynchronously.

> I don't know if we actually need to lock anymore now that each query is a single GRPC request with the proto changes. I think the only reason we needed to lock before was that we first had to send components and then the query and we had to guarantee the order. I'm not sure about J-ecdar though but I would suspect that it will just blocks on the server side, so we still do not need to lock on our side.

> This is probably a larger change, since we actually only want to spin up a single instance of Reveaal now and send it async queries instead of blocking, so I think we should leave it to a future PR

_Originally posted by @seblund in https://github.com/Ecdar/Ecdar-Test/pull/27#discussion_r1209296036_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.