You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: