-
Notifications
You must be signed in to change notification settings - Fork 14
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
Encoder Progress / Source Progress #3
Comments
For progress of the Encoder, reporting can be had by integrating with gen_event, although some custom structs will be defined to represent the possible range of events. For progress of each Source, that may have to be done as an opt-in thing as support for custom sources has now been implemented and will come up soon. Further thinking required. |
I have kind of sorted this out for the Encoder but need more design for Sources to participate. |
@alvises Please take a look at #5 esp. As to Source progress, since not all Sources know how many bytes they need to read (sometimes you don’t have this information, for example if you are reading from a connection that is serving a Packmatic stream 😛), I am thinking of something optional. For example, the signature of |
handler_fun = fn event ->
:ok = Process.send(parent, event, [:noconnect, :nosuspend])
end
Packmatic.build_stream(on_error: :skip, on_event: handler_fun) Really nice! Exactly what I meant :) |
@alvises 👋 This is good news, I shall merge this soon. |
That's great!! |
This is merged into develop and a new release on Hex will be coming tomorrow. |
It would be nice to have a way to know the progress of compression and, in case of
:url
entries download progress as well.The two options I have in mind are:
Packmatic.build_stream/2
in the options.The text was updated successfully, but these errors were encountered: