.. efun:: int binary_message(int *|string message, int flags)

  Flush output and send output directly with write **without IAC quoting**. The message may contain zeroes if given as int *. The messages go to ``this_object()``, but only if it is interactive. It returns the number of characters actually written. Any 'allowed charset' setting is ignored.

  .. todo:: This doc is leaking implementation details (ex, add_message references) instead of explaining the topic to people who aren't familiar with the source.

  Flag settings are interpreted bitwise and may be ored together (only for clients not using :topic:`MCCP` compression):

  Bit 0 (value 1)
    when set, ``add_message()`` is used instead of ``write()``. Thus no previous flushing of the buffer is needed, but the output is not immediate, nor can the number of bytes actually sent be determined - the return value is undefined.

  Bit 1 (value 2)
    The buffer is flushed _after_ adding the message. Useful only in conjunction with Bit 0.

  The idea behind the flag settings is that sending command codes for colours and other things needs to bypass the allowed charset filters, but isn't important enough to waste bandwith on a synchronous transmission.

  :history 3.2.1@40 introduced:
  :history 3.2.1@60 changed: Argument 'flags' introduced.

  .. seealso:: :efun:`set_connection_charset`