Prepends this command with a number of other writes.
Prepends this command with a number of other writes.
The first element of the given Iterable becomes the first sub write of a potentially
created CompoundWrite.
Prepends this command with another Write or WriteFile to form
a CompoundWrite.
Prepends this command with another Write or WriteFile to form
a CompoundWrite.
The acknowledgment token associated with this write command.
The acknowledgment token associated with this write command.
Java API: appends this command with another WriteCommand to form a CompoundWrite.
Java API: appends this command with another WriteCommand to form a CompoundWrite.
Java API: prepends this command with a number of other writes.
Java API: prepends this command with a number of other writes.
The first element of the given Iterable becomes the first sub write of a potentially
created CompoundWrite.
Java API: prepends this command with another Write or WriteFile to form
a CompoundWrite.
Java API: prepends this command with another Write or WriteFile to form
a CompoundWrite.
An acknowledgment is only sent if this write command “wants an ack”, which is equivalent to the #ack token not being a of type NoAck.
An acknowledgment is only sent if this write command “wants an ack”, which is equivalent to the #ack token not being a of type NoAck.
(Since version ) see corresponding Javadoc for more information.
Write
countbytes starting atpositionfrom file atfilePathto the connection. The count must be > 0. The connection actor will reply with a CommandFailed message if the write could not be enqueued. If WriteCommand#wantsAck returns true, the connection actor will reply with the supplied WriteCommand#ack token once the write has been successfully enqueued to the O/S kernel. Note that this does not in any way guarantee that the data will be or have been sent! Unfortunately there is no way to determine whether a particular write has been sent by the O/S.