Class Arm.MoveThroughJointPositionsStreamedResponse.BatchAck

java.lang.Object
com.google.protobuf.AbstractMessageLite<Arm.MoveThroughJointPositionsStreamedResponse.BatchAck,Arm.MoveThroughJointPositionsStreamedResponse.BatchAck.Builder>
com.google.protobuf.GeneratedMessageLite<Arm.MoveThroughJointPositionsStreamedResponse.BatchAck,Arm.MoveThroughJointPositionsStreamedResponse.BatchAck.Builder>
com.viam.component.arm.v1.Arm.MoveThroughJointPositionsStreamedResponse.BatchAck
All Implemented Interfaces:
com.google.protobuf.MessageLite, com.google.protobuf.MessageLiteOrBuilder, Arm.MoveThroughJointPositionsStreamedResponse.BatchAckOrBuilder
Enclosing class:
Arm.MoveThroughJointPositionsStreamedResponse

public static final class Arm.MoveThroughJointPositionsStreamedResponse.BatchAck extends com.google.protobuf.GeneratedMessageLite<Arm.MoveThroughJointPositionsStreamedResponse.BatchAck,Arm.MoveThroughJointPositionsStreamedResponse.BatchAck.Builder> implements Arm.MoveThroughJointPositionsStreamedResponse.BatchAckOrBuilder
 BatchAck is returned by arm implementations to ack a
 `TrajectoryBatch`. Due to the lack of actionable payload in
 `BatchAck`, Arm implementations are not currently obligated to
 ack every batch, or even any batch. It is currently unspecified
 whether ack'ing a batch indicates its acceptance, issue to the
 arm, or completion. These very relaxed requirements may become
 tighter if and when `BatchAck` messages begin carrying meaningful
 payloads back to the client. For now, the recommended practice
 for arm implementors is to ack each batch that has been
 successfully issued/enqueued to the arm.
 
Protobuf type viam.component.arm.v1.MoveThroughJointPositionsStreamedResponse.BatchAck