Uses of Package
org.microproxy.contentviews

Packages that use org.microproxy.contentviews
  • Class
    Description
    Turns a message body into readable text: protobuf as YAML with field numbers, gRPC message by message, msgpack, form data, GraphQL, and so on.
    What a view knows about a body besides its bytes.
    A set of ContentViews, and the choice among them.
    A body rendered by a view.
    Data that a decoder or ContentView cannot make sense of: malformed protobuf, a truncated gRPC frame, an unknown compression, invalid msgpack, JSON or multipart data.
    One entry of a status's details: a google.protobuf.Any.
    One framed message, as it is on the wire.
    A google.rpc.Status, as servers send it in grpc-status-details-bin.
    One field of a decoded protobuf message, as it appeared on the wire.
    A decoded protobuf message: its fields in the order they appeared on the wire.
    Protobuf type definitions, read from a FileDescriptorSet (what protoc --descriptor_set_out=types.desc --include_imports writes), so that messages decode with field names, enum names and declared types instead of guesses, and gRPC calls decode with their method's input and output types:
    An enum type.
    A field of a message type.
    A message type: its full name and fields.
    An RPC method of a service.
    The types a field can be declared with, as numbered in descriptor.proto.
    One value of a protobuf field: what its wire type says, plus how a length-delimited value was understood.
  • Class
    Description
    A set of ContentViews, and the choice among them.
  • Class
    Description
    A set of ContentViews, and the choice among them.
    A body rendered by a view.
    Data that a decoder or ContentView cannot make sense of: malformed protobuf, a truncated gRPC frame, an unknown compression, invalid msgpack, JSON or multipart data.
    A decoded protobuf message: its fields in the order they appeared on the wire.
    Protobuf type definitions, read from a FileDescriptorSet (what protoc --descriptor_set_out=types.desc --include_imports writes), so that messages decode with field names, enum names and declared types instead of guesses, and gRPC calls decode with their method's input and output types:
  • Class
    Description
    Protobuf type definitions, read from a FileDescriptorSet (what protoc --descriptor_set_out=types.desc --include_imports writes), so that messages decode with field names, enum names and declared types instead of guesses, and gRPC calls decode with their method's input and output types: