Describe MobilityAPI's reference implementation as the compiled Go tier#13
Open
estebanzimanyi wants to merge 1 commit into
Open
Describe MobilityAPI's reference implementation as the compiled Go tier#13estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
The MobilityAPI reference implementation is a thin, compiled Go server that runs all temporal work and (de)serialization inside MobilityDB, with no in-process MEOS; a PyMEOS-based Python implementation is also available. Update the HTTP/API layer entry and the PyMEOS bindings entry on the ecosystem profile to match.
estebanzimanyi
force-pushed
the
docs/mobilityapi-go-reference
branch
from
15e3aaa to
72799ad
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MobilityAPI reference implementation is a thin, compiled Go server that runs all temporal work and (de)serialization inside MobilityDB, with no in-process MEOS; a Python proof-of-concept also exists. This updates the HTTP/API layer entry and the PyMEOS bindings entry on the ecosystem profile to match.