Module lyntin.net

This holds the SocketCommunicator class which handles socket connections with a mud and polling the connection for data.

  When the mud sends a bell character, we spam this hook.  Typically
  the ui's will register with this hook and handle the bell however
  they see fit.

  Arg mapping: { "session": Session }

  session - the session that received the bell

  We try to do some prompt detection and separate prompts into their
  own events (separate from mud data).

  Arg mapping: { "session": Session, "prompt": string }

  session - the Session that this prompt came from

  prompt - the prompt string

  This hook gets spammed every time we make a successful connection.

  Arg mapping: { "session": Session, "host": String, "port": int }

  session - the Session object for this connection

  host - the host we connected to

  port - the port number for the host

  This allows you to filter incoming data before it passes through
  Lyntin.  If you were going to write an MCCP module, this is the
  hook it would register with to decompress incoming mud data.

  Functions that register with this hook should return the dataadj
  if they did nothing or the adjusted dataadj if they transformed it.
  Look at the user_filter_hook examples in the alias and speedwalk
  modules.

  Arg mapping: { "session": Session, "data": String, "dataadj": String }

  session - the Session that this data came from

  data - the original data we got from the mud

  dataadj - the data the previous function in the hook returned

  This allows you to filter outgoing data after it has passed through
  Lyntin and just before it gets sent out on the socket.  If you were 
  going to write an MCCP module, this is the hook it would register 
  with to compress outgoing mud data.

  Functions that register with this hook should return the dataadj
  if they did nothing or the adjusted dataadj if they transformed it.
  Look at the user_filter_hook examples in the alias and speedwalk
  modules.

  Arg mapping: { "session": Session, "data": String, "dataadj": String }

  session - the Session that this data is going to

  data - the original data we wanted to send to the mud

  dataadj - the data the previous function in the hook returned

  There are a series of Telnet options that Lyntin doesn't handle.
  So we allow module writers to handle them if they so desire.
  The data argument is the telnet option string.  So if they
  send us 255 251 24, then that's what you're getting.  We handle
  all the buffering of telnet option stuff--so you needn't worry
  about that.

  We send along the IAC DO TERMTYPE kinds of things as well as the
  IAC SB blah blah IAC SE kinds of things.  This is a handler--so
  if you've handled it, raise an exported.StopSpammingException() .

  Arg mapping: { "session": Session, "data": String }

  session - the Session that this telnet option came from

  data - the telnet option itself