!Q@L"T      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSNone warp-grpc3Helper to set the GRPCStatus on the trailers reply.NoneX  warp-grpcUntyped gRPC Service handler. warp-grpc"Path to the Service to be handled. warp-grpcActual request handler. warp-grpcA Wai Handler for a request. warp-grpc Build a WAI T from a list of ServiceHandler.Currently, gRPC calls are lookuped up by traversing the list of ServiceHandler. This lookup may be inefficient for large amount of servics. warp-grpc.Aborts a GRPC handler with a given GRPCStatus. warp-grpc Build a WAI  Middleware from a list of ServiceHandler.Currently, gRPC calls are lookuped up by traversing the list of ServiceHandler. This lookup may be inefficient for large amount of services. warp-grpc/Looks-up header for encoding outgoing messages.  warp-grpc?Looks-up the compression to use from a set of known algorithms.! warp-grpc/Looks-up header for decoding incoming messages." warp-grpc6Looks-up the compression to use for decoding messages. warp-grpc#Compression for the request inputs. warp-grpc$Compression for the request outputs. warp-grpcRequest object. warp-grpc Write a data chunk in the reply. warp-grpcFlush the output.  !"  !"None .HSVX_A!# warp-grpc9Handler to decide on the next message (if any) to return.& warp-grpc3Pair of handlers for reacting to incoming messages.* warp-grpcHA GeneralStreamHandler combining server and client asynchronous streams.2 warp-grpcHandy type for 'bidirectional-streaming' RPCs.We expect an implementation to: - acknowlege a new bidirection stream by returning an initial state and one functions: - a state-passing function that returns a single action step The action may be to - stop immediately - wait and handle some input with a callback and a finalizer (if the client closes the stream on its side) that may change the state - return a value and a new statevThere is no way to stop locally (that would mean sending HTTP2 trailers) and keep receiving messages from the client.7 warp-grpcHandy type for 'client-streaming' RPCs.We expect an implementation to: - acknowledge a the new client stream by returning an initial state and two functions: - a state-passing handler for new client message - a state-aware handler for answering the client when it is ending its stream See 30 for the type which embodies these requirements.; warp-grpcHandy type for 'server-streaming' RPCs.We expect an implementation to: - read the input request - return an initial state and an state-passing action that the server code will call to fetch the output to send to the client (or close an a Nothing) See 80 for the type which embodies these requirements.< warp-grpc#Handy type to refer to Handler for = RPCs handler.= warp-grpc-Construct a handler for handling a unary RPC.> warp-grpc8Construct a handler for handling a server-streaming RPC.? warp-grpc8Construct a handler for handling a client-streaming RPC.@ warp-grpc?Construct a handler for handling a bidirectional-streaming RPC.A warp-grpc?Construct a handler for handling a bidirectional-streaming RPC.B warp-grpcHandle unary RPCs.C warp-grpcHandle Server-Streaming RPCs.D warp-grpcHandle Client-Streaming RPCs.E warp-grpc$Handle Bidirectional-Streaming RPCs.F warp-grpcHandler for the somewhat general case where two threads behave concurrently: - one reads messages from the client - one returns messages to the clientG warp-grpc#Helpers to consume input in chunks.H warp-grpc9Combinator around message handler to error on left overs.This combinator ensures that, unless for client stream, an unparsed piece of data with a correctly-read message is treated as an error.G warp-grpcMessage decoder. warp-grpcKHandler for a single message. The ByteString corresponds to leftover data. warp-grpc$Handler for handling end-of-streams. warp-grpc"Action to retrieve the next chunk.&#$%&')(*+,-.10/23465789:;<=>?@ABCDEFGH&<;89:734652.10/+,-=>?@ABCDE*&')(#$%FGHNoneB#$%&'()*+,-./0123456789:;<IJKLM<I;89:J73456K2./01+,-L*&'()#$%MNoneC#$%&'()*+,-./0123456789:;<NOPQR<N;89:O73456P2./01+,-Q*&'()#$%RNone EHSVX_IS warp-grpc=Helper to constructs and serve a gRPC over HTTP2 application.You may want to use , for adding middlewares to your gRPC server.S warp-grpc"TLS settings for the HTTP2 server. warp-grpcWarp settings. warp-grpc!List of ServiceHandler. Refer to grcpApp warp-grpcCompression methods used.9 #$%&'()*+,-./0123456789:;<NOPQRS9S<;89:734562+,-./01*&'()#$%NOPQR SafeKUVWXYZ[\]                      !""#$%&'()*+,--.//01233456789::;<=>>?@ABCDEFGHIJKLMBCDEFBCDEFNOPQRSTUVWXYZwarp-grpc-0.4.0.1-inplaceNetwork.GRPC.ServerNetwork.GRPC.Server.HelpersNetwork.GRPC.Server.Wai"Network.GRPC.Server.Handlers.Trans#Network.GRPC.Server.Handlers.UnliftNetwork.GRPC.Server.HandlersPaths_warp_grpcbaseGHC.IOthrowIO http2-grpc-typs-0.5.0.0-a7785fc4Network.GRPC.HTTP2.Types DATA_LOSS UNAVAILABLEINTERNAL UNIMPLEMENTED OUT_OF_RANGEABORTEDFAILED_PRECONDITIONRESOURCE_EXHAUSTEDUNAUTHENTICATEDPERMISSION_DENIEDALREADY_EXISTS NOT_FOUNDDEADLINE_EXCEEDEDINVALID_ARGUMENTUNKNOWN CANCELLEDOKGRPCStatusCodeGRPCStatusMessage GRPCStatusmodifyGRPCStatusServiceHandlergrpcHandlerPathgrpcWaiHandler WaiHandlergrpcApp closeEarly grpcServicerequestAcceptEncodingNameslookupEncodingrequestDecodingNamelookupDecodingOutgoingStreamoutgoingStreamNextIncomingStreamincomingStreamHandlerincomingStreamFinalizerGeneralStreamHandler BiDiStream bidirNextStepBiDiStepAbort WaitInput WriteOutputBiDiStreamHandler ClientStreamclientStreamHandlerclientStreamFinalizerClientStreamHandler ServerStreamserverStreamNextServerStreamHandler UnaryHandlerunary serverStream clientStream bidiStream generalStream handleUnaryhandleServerStreamhandleClientStreamhandleBiDiStreamhandleGeneralStreamhandleRequestChunksLooperrorOnLeftOverrunGrpcw-3.2.2.1-4c9279af Network.Wai Applicationversion getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName