<commit_before># Localtunnel Protocol

The Localtunnel Protocol (LTP) defines a lightweight protocol for a
client and server to establish a pool of connections used to proxy
connections from the server to the client. 

Editor: <NAME> <<EMAIL>><br />
Contributors: <NAME> <<EMAIL>>

## License

Copyright (c) 2012 <NAME>.

This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This Specification is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

## Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119[1].

## Goals

* Allow TCP connections to flow from the server to the client, where the
  server acts as a reverse proxy and the client provides backend
connections
* Avoid overhead of multiplexing by using one backend connection to
  tunnel each frontend conection
* Separate control channel from proxy channels as separate connections
* Allow long-lived tunnel sessions with heartbeating

## Overview

             +--------------------+
             | Localtunnel Server |
             |--------------------|         +----------+<commit_msg>email formatting<commit_after># Localtunnel Protocol

The Localtunnel Protocol (LTP) defines a lightweight protocol for a
client and server to establish a pool of connections used to proxy
connections from the server to the client. 

Editor: <NAME> <<<EMAIL>>><br />
Contributors: <NAME> <<<EMAIL>>>

## License

Copyright (c) 2012 <NAME>.

This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This Specification is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

## Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119[1].

## Goals

* Allow TCP connections to flow from the server to the client, where the
  server acts as a reverse proxy and the client provides backend
connections
* Avoid overhead of multiplexing by using one backend connection to
  tunnel each frontend conection
* Separate control channel from proxy channels as separate connections
* Allow long-lived tunnel sessions with heartbeating

## Overview

             +--------------------+
             | Localtunnel Server |
             |--------------------|         +----------+
{'fraction_non_alphanumeric': 0.09344, 'fraction_numerical': 0.0064, 'mean_word_length': 3.5043227665706054, 'pattern_counts': {'":': 0, '<': 21, '<?xml version=': 0, '>': 21, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3565165', 'n_tokens_mistral': 785, 'n_tokens_neox': 737, 'n_words': 421}