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

Implement LocatedAtStream as a proper HTTP based stream #5

Open
asorici opened this issue Aug 17, 2024 · 0 comments
Open

Implement LocatedAtStream as a proper HTTP based stream #5

asorici opened this issue Aug 17, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@asorici
Copy link

asorici commented Aug 17, 2024

CONTEXT

LocatedAtContextStream is currently implemented as a local stream that is started when the ContextMgmtVerticle is started.
We want to replace this with a proper HTTP based version, where the stream starts independently of the ContextMgmtVerticle that consumes it.

TODO

Check out the literature and existing code support for Web-based streams. E.g.:

The last resort solution is to implement a demo version where:
- some HTTP client repeatedly sends the LocatedAt RDF content -- this doesn't have to be JAVA anymore - it can be a simple Python script
- some HTTP server (running as a Verticle, for example) receives it and inserts it into the existing local stream. This means we keep the local stream setup in ContextMgmtVerticle, but its contents are not locally generated, but rather come from a remote HTTP client

@asorici asorici added the enhancement New feature or request label Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants