John Ewart

@artursouza and I were talking about this earlier and I opened a PR to deprecate the HTTP-transport bits; we could get rid of some code it seems that it could...

(Fixed the placement image, there were previously two duplicate Actor entities)

@olitomlinson -- I think those are great questions so thanks for asking them! I will avoid sounding like an echo chamber since Chris, Hal and Yaron mostly answered everyone's questions...

I don't have any strong opinion other than making things clear and easy to use -- in that regard I think that using only the `Component` CRD with some metadata...

The intention of this is to provide Spring-cloud compatible annotations (i.e `@EnableDiscoveryClient`) using the `dapr/java-sdk` talk to Dapr instead of another service or library, right? So, as a trivial example,...

My question (and I can put this in #626) is this -- are we going to effectively write-off Java 8 users? According to New Relic's numbers from earlier this year,...

As much as I would love it, I suspect there is not much beyond anecdotal data points. From my perspective this proposal is actually somewhat independent of the Java SDK...

> In addition, we need to log warning if the HTTP protocol is chosen via the property we provide in the SDK, this way the user will see the warning...

Fixed checkstyle errors, removed one of the depreciation tags as requested and also added signoff -- amended and force pushed to keep things simpler.

Created proposal #794 to track this