Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tracking Issue for Handler Registry being experimental.

See original GitHub issue

We’re currently marking all of the HandlerRegistries as ExperimentalAPI. We should decide on the appropriate interface and move toward making them public.

Issue Analytics

State:
Created 8 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

ejona86commented, Nov 16, 2017

API review:

stabilize HandlerRegistry as-is (leaving getServices() experimental)
stabilize ServerBuilder.fallbackHandlerRegistry
No qualms with MutableHandlerRegistry. But want to delaying stabilizing things in util until we split grpc-api out of core.

0reactions

zhangkun83commented, Jun 14, 2016

Now ServerCallHandler is non-experimental. HandlerRegistry-related code will remain experimental in 1.0.

Top Results From Across the Web

Azure Service Bus end-to-end tracing and diagnostics

One part of this problem is tracking logical pieces of work. It includes message processing result and latency and external dependency calls ...

Error Tracking - GitLab Docs

Error Tracking allows developers to easily discover and view the errors that their application may be generating. By surfacing error information where the ......

Instant Tracking Wikitude SDK Windows Native API 9.4.0 ...

The instant tracking algorithm requires another input value to be provided in the ... This event handler supplies a InstantTracker and the current ......

Process | Node.js v19.2.0 Documentation

The process.exit() method being called explicitly;; The Node.js event loop no ... This is useful for tracking potential errors in an application while...

Add a listener - Optimizely for Web

Your handler function will be invoked for each applicable lifecycle event that occurs after the handler is registered. It is not retroactively invoked...