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

Using separete process service for sending reports. #327

Closed
romansl opened this Issue Nov 20, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@romansl
Contributor

romansl commented Nov 20, 2015

Related to #313.

Seems I found the solution for this problem. You should just put the SendWorker into separete process.

Here is example of my HockeyApp Sender: https://gist.github.com/romansl/5c5c8e756ad20001ba8f

What do you think?

@william-ferguson-au

This comment has been minimized.

Show comment
Hide comment
@william-ferguson-au

william-ferguson-au Nov 20, 2015

Member

That's a pretty neat idea.

I'm inclined to think that we should use that as the default sender.
It would mean that the crash could always get reported immediately.

Want to put together a PR?

Member

william-ferguson-au commented Nov 20, 2015

That's a pretty neat idea.

I'm inclined to think that we should use that as the default sender.
It would mean that the crash could always get reported immediately.

Want to put together a PR?

@romansl

This comment has been minimized.

Show comment
Hide comment
@romansl

romansl Nov 23, 2015

Contributor

Here: #329

Contributor

romansl commented Nov 23, 2015

Here: #329

@william-ferguson-au

This comment has been minimized.

Show comment
Hide comment
@william-ferguson-au

william-ferguson-au Jan 4, 2016

Member

Thanks for your help on this @romansl

Member

william-ferguson-au commented Jan 4, 2016

Thanks for your help on this @romansl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment