Class PeerFetch

javascript/src/peerfetch.ts:18–648

 *
*/
export class PeerFetch {

  /**
   * A PeerJS instance that provides lower layer p2p connectivity API
   */
  private _peer?: Peer

  /**
   * Configuration parameters for the p2p network connection.
   */
  private _config: Peer.PeerJSOption

  /**
   * An identifier of this PeerJS instance that is unique within the p2p network that it participates.
   * It is assigned by the signaling server. Similar to an http session ID.
   */
  private _myPeerId?: string

  /**
   * Peer ID of the remote node that will proxy http requests
   */
  private _remotePeerID?: string

  /**
   * Tracks current status of the connection to the signaling server
   */
  private _signalingConnectionStatus: ConnectionStatus = ConnectionStatus.DISCONNECTED

  /**
   * Tracks current status of the connection to the remote peer
   */
  private _peerConnectionStatus: ConnectionStatus = ConnectionStatus.DISCONNECTED

  /**
   * The current peer data connection that http requests ride on.
   * Currently a single peer data connection is managed per PeerFetch instance.
   */
  private _dataConnection?: Peer.DataConnection

  /**
   * Map of pending HTTP requests
   */
  private _requestMap: Map<number, any> = new Map()

  /**
   * Refernce to a timer that runs keepalive pings to the remote peer.
   */
  private _keepAlive?: ReturnType<typeof setTimeout>

  /**
   * Ticketing enforces a strict order or processing for pending http requests and corresponding responses.
   * Each async request from client code draws a new ticket.
   * Tickets are processed in the sequential monotonic order that they are drawn.
   * Once a request is fully processed, its ticket is burned and the next ticket is processed.
   * A request ticket is not fully processed until the corresponding final HTTP response is received.
   *
   * /