Package io.deephaven.server.session

Class TicketResolverBase

java.lang.Object

io.deephaven.server.session.PathResolverPrefixedBase

io.deephaven.server.session.TicketResolverBase

All Implemented Interfaces:

PathResolver, TicketResolver

Direct Known Subclasses:

ApplicationTicketResolver, ExportTicketResolver, ScopeTicketResolver, SharedTicketResolver

public abstract class TicketResolverBase
extends PathResolverPrefixedBase

Nested Class Summary

Nested classes/interfaces inherited from interface io.deephaven.server.session.TicketResolver

TicketResolver.Authorization

Field Summary

Fields

Modifier and Type	Field	Description
protected final TicketResolver.Authorization	authorization

Constructor Summary

Constructors

Constructor	Description
TicketResolverBase(AuthorizationProvider authProvider, byte ticketPrefix, String flightDescriptorRoute)

Method Summary

Modifier and Type	Method	Description
final byte	ticketRoute()	Tickets are disambiguated by their first byte.

Methods inherited from class io.deephaven.server.session.PathResolverPrefixedBase

flightDescriptorRoute, handlesPath

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface io.deephaven.server.session.TicketResolver

flightInfoFor, forAllFlightInfo, getLogNameFor, publish, publish, publish, resolve, resolve

Field Details

authorization

protected final TicketResolver.Authorization authorization

Constructor Details

TicketResolverBase

public TicketResolverBase(AuthorizationProvider authProvider,
 byte ticketPrefix,
 String flightDescriptorRoute)

Method Details

ticketRoute

public final byte ticketRoute()

Description copied from interface: TicketResolver

Tickets are disambiguated by their first byte. Each resolver claims one byte; and there may not be any duplicates. Some ticket resolvers do not produce any tickets, but rather depend entirely on Flight descriptors, in which case they do not require a byte, in those cases the resolver should return 0 indicating that no ticket prefix is necessary.

Returns:

the single byte prefix used as a route on the ticket; or zero for no ticket resolution