Stream: android
Topic: cql evaluator interface design
JP (Apr 06 2022 at 18:10):
I'm working through some considerations for creating a better set of APIs for integrating the cql-evaluator on various platforms, including Android. Some thoughts are documented here:
https://github.com/DBCG/cql-evaluator/discussions/90
It's a rough draft and still missing a few diagrams. I'll add those as I complete them
@Jing Tang @Vitor Pamplona
JP (Apr 06 2022 at 18:10):
Apologies for the delay on this Jing/Vitor. Meant to get this done Monday but got sidetracked.
JP (Apr 06 2022 at 18:11):
Also, @Bryn Rhodes
JP (Apr 11 2022 at 23:13):
@Jing Tang @Vitor Pamplona - Sketeched out "Design 3" as discussed this morning, and added Android loading to the considerations in the doc. Reviewed the doc with Bryn, who is going to comment as well.
Vitor Pamplona (Apr 12 2022 at 14:00):
This 3rd option feels better.
Vitor Pamplona (Apr 12 2022 at 14:02):
Does it make sense to change these interfaces' names to start with I, like HAPI does?
Vitor Pamplona (Apr 12 2022 at 14:08):
@Jing Tang does the Android SDK have support for the transaction API?
JP (Apr 12 2022 at 16:47):
The general Java convention is to not use the I prefix, but HAPI does do that. I don't have a strong preference either way.
Bryn also provided the feedback that the return type for search should be a Bundle. I updated design 3 to reflect that.
Last updated: Apr 12 2022 at 19:14 UTC
