A take on re-implementing channels (WIP- don't merge)

This is WIP and not yet finished.

I agree. With web sockets support, having REST on client side would be
redundant.


On Tue, Sep 2, 2014 at 10:19 AM, Nitesh Kant <notifications@github.com>
wrote:

> In
> eureka-client/src/main/java/com/netflix/eureka/client/service/EurekaServiceImpl.java:
>
> >
> > -    public EurekaServiceImpl(TransportClientProvider<DiscoveryClient> discoveryClientProvider,
> > -                             TransportClientProvider<RegistrationClient> registrationClientProvider) {
> > -        registrationChannelMonitor = new RegistrationChannelMonitor(registrationClientProvider);
> > -        registrationChannelMonitor.start();
> > +    protected EurekaServiceImpl(boolean readClient, TransportClient aClient) {
>
> I haven't thought completely over the request-response style communication
> but from the client end we do not need it as we will always use full duplex
> communication, rite?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Netflix/eureka/pull/187/files#r17001060>.
>