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

Event object design #14

Open
okumin opened this issue May 29, 2017 · 0 comments
Open

Event object design #14

okumin opened this issue May 29, 2017 · 0 comments

Comments

@okumin
Copy link
Owner

@okumin okumin commented May 29, 2017

The first implementation of event object is here.

EventStream has a tag and forwarded messages(entries) in a request.
Entries is a List<EventEntry> and EventEntry is an event(e.g. a line of a log file).

I'm thinking to provide following APIs.

  • on demand decoding
    • Influent decodes requests and transform messagepack into List<EventEntry> eagerly
    • lazy decoding saves CPUs in some cases
      • when Influent forwards requests like a proxy
      • when Influent writes requests to file and reads those later like a buffer plugin
  • POJO mapping API
@okumin okumin mentioned this issue Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.