class EventMachine::Connection

{EventMachine::Connection#close_connection_after_writing}.
yet been sent across the network. If you want to avoid this behavior, use
sent to the connection using {EventMachine::Connection#send_data} but which has not
{#close_connection} will *silently discard* any outbound data which you have

this behavior.
However, it's not guaranteed that a future version of EventMachine will not change
the unbind callback will not re-enter your code "inside" of your call to close_connection.
take place sometime after your call to close_connection completes. In other words,
after you call close_connection. You may assume that the unbind callback will
will callback the unbind method for the particular connection at a point shortly
the connection is closed when close_connection returns. In particular, the framework
at the next available opportunity within the event loop. You may not assume that
you want to close. close_connection schedules the connection to be closed
callback handler, whether or not the callback was made against the connection
by the event loop. You may call this method against a connection object in any
EventMachine::Connection#close_connection is called only by user code, and never

def close_connection after_writing = false
  EventMachine::close_connection @signature, after_writing
end