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

Plan for Projections? #2

Open
berkes opened this issue Oct 5, 2020 · 0 comments
Open

Plan for Projections? #2

berkes opened this issue Oct 5, 2020 · 0 comments

Comments

@berkes
Copy link

berkes commented Oct 5, 2020

I'm trying to find out the bounds of this library: to know, if I choose this as basis, what I'll have to implement myself outside of this lib.

Right now, there is no projection in place. Nor do I see any mention of other event-processors (WorkFlows, Reactors, etc) in the code or the readme.

I'm currently in need of an event-source system that projects data into files (KML/GML/XML) and into a database (PostGIS).

Is this planned as part of this library? Or is this deliberately left out of the library and left for the implementer?

If the latter, it might be a good idea to outline some additional requirements (or a sample implementation), so that an implementer has something stable-ish to work against. E.g. a processor might need to implement mutex-locks and/or cursors; whose implementation depends greatly on details such as the ID of-, ordering of-, delivery of- events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant