Http.shutdown() Needs to Be Called Explicitly?

90 views
Skip to first unread message

Ji ZHANG

unread,
Jan 26, 2015, 2:30:07 AM1/26/15
to dispatc...@googlegroups.com
Hi,

I'm using dispatch 0.11.2, and it seems that the packaged jar just won't quit. I googled a lot and did some experiments, found out that Http.shutdown() must be called explicitly.

I checked out the source code, and sees Http is an object that'll automatically initiate with a new http-async-client. So even if I use 'val http = new Http();...;http.shutdown()', the Http still needs to be shutdown.

Is it designed so? If I want to use dispatch in a library, does it mean I need to let the library user shutdown Http explicitly?

I found out that in sbt everything works fine, but I don't understand how SbtProcessDefaults works. I tried sys.addShutdownHook(() => Http.shutdown()), with no luck.

So I'm wondering whether there's a simple way to to implicitly shutdown Http, or not start it at all. Besides, the new documentation mentions nothing about shutdown...

Thanks.
Reply all
Reply to author
Forward
0 new messages