Examples of writeBinary()

• com.facebook.presto.hive.shaded.org.apache.thrift.protocol.TTupleProtocol.writeBinary()
• com.facebook.thrift.protocol.TBinaryProtocol.writeBinary()
• com.facebook.thrift.protocol.TProtocol.writeBinary()
• com.fasterxml.jackson.core.JsonGenerator.writeBinary()
  Method that will output given chunk of binary data as base64 encoded, as a complete String value (surrounded by double quotes). This method defaults

  Note: because Json Strings can not contain unescaped linefeeds, if linefeeds are included (as per last argument), they must be escaped. This adds overhead for decoding without improving readability. Alternatively if linefeeds are not included, resulting String value may violate the requirement of base64 RFC which mandates line-length of 76 characters and use of linefeeds. However, all {@link JsonParser} implementationsare required to accept such "long line base64"; as do typical production-level base64 decoders. @param bv Base64 variant to use: defines details such aswhether padding is used (and if so, using which character); what is the maximum line length before adding linefeed, and also the underlying alphabet to use.

• org.apache.thrift.protocol.TBinaryProtocol.writeBinary()
• org.apache.thrift.protocol.TProtocol.writeBinary()
• org.apache.thrift.protocol.TTupleProtocol.writeBinary()
• org.codehaus.jackson.JsonGenerator.writeBinary()
  Method that will output given chunk of binary data as base64 encoded, as a complete String value (surrounded by double quotes). This method defaults

  Note: because Json Strings can not contain unescaped linefeeds, if linefeeds are included (as per last argument), they must be escaped. This adds overhead for decoding without improving readability. Alternatively if linefeeds are not included, resulting String value may violate the requirement of base64 RFC which mandates line-length of 76 characters and use of linefeeds. However, all {@link JsonParser} implementationsare required to accept such "long line base64"; as do typical production-level base64 decoders. @param b64variant Base64 variant to use: defines details such aswhether padding is used (and if so, using which character); what is the maximum line length before adding linefeed, and also the underlying alphabet to use.

• org.codehaus.stax2.XMLStreamWriter2.writeBinary()
• org.gradle.messaging.serialize.FlushableEncoder.writeBinary()
• org.gradle.messaging.serialize.OutputStreamBackedEncoder.writeBinary()
• org.jvnet.staxex.XMLStreamWriterEx.writeBinary()
  Write the binary data.

  Conceptually (infoset-wise), this produces the base64-encoded binary data on the output. But this allows implementations like FastInfoset or XOP to do the smart thing.

  The use of this method has some restriction to support XOP. Namely, this method must be invoked as a sole content of an element.

  (data,start,len) triplet identifies the binary data to be written. After the method invocation, the callee owns the buffer. @param contentType this mandatory parameter identifies the MIME type of the binary data. If the MIME type isn't known by the caller, "application/octet-stream" can be always used to indicate "I don't know." Never null.

• org.openntf.domino.Document.writeBinary()
• org.postgis.binary.BinaryWriter.writeBinary()
  Write a binary encoded geometry. Is synchronized to protect offset counter. (Unfortunately, Java does not have neither call by reference nor multiple return values.) This is a TODO item. The geometry you put in must be consistent, geom.checkConsistency() must return true. If not, the result may be invalid WKB. @see Geometry#checkConsistency()

Examples of org.postgis.binary.BinaryWriter.writeBinary()