<commit_before>###Reasoning:

This projects is easing the pain of doing ad-hoc testing of TCP based servers. It shouldn't be even considered alpha - this is a learning project, whose only purpose was to make me use:

* [dropwizard](http://www.dropwizard.io/),
* [netty](http://netty.io/)
* and [emberjs](http://emberjs.com/)

I didn't had an opportunity to do so during my normal job and always wanted to do something more ambitious using mentioned tools.

On a daily basis, I'm working with servers using [Extensible Provisioning Protocol](http://tools.ietf.org/html/rfc5730). Most of the code is old enough to remember the beginnings of steam engines (or at least it feels like that), I wanted to create a programmable tool which might ease the pain of testing parts of the non-testable (legacy) server calls. Without any refactorings, the easiest way of doing this is by directly sending EPP messages and validating the responses.

While implementing the whole tool, I will try to be generic enough, so introduction of new protocols which the server will be capable of speaking to, should be relatively straightforward.

Readme will be updated as more features will be added.<commit_msg>minor readme fixes.<commit_after>###Reasoning:

This projects is easing the pain of doing ad-hoc testing of TCP based servers. It shouldn't be even considered alpha - this is a learning project, whose only purpose was to make me use:

* [dropwizard](http://www.dropwizard.io/),
* [netty](http://netty.io/)
* and [emberjs](http://emberjs.com/)

I didn't had an opportunity to do so during my normal job and always wanted to do something more ambitious using mentioned tools.

On a daily basis, I'm working with servers using [Extensible Provisioning Protocol](http://tools.ietf.org/html/rfc5730). Most of the code is old enough to remember the beginnings of steam engines (or at least it feels like that), I wanted to create a programmable tool which might ease the pain of testing parts of the non-testable (legacy) server calls. Without any refactorings, the easiest way of doing this is by directly sending EPP messages to test servers and validating the responses.

While implementing the whole tool, I will try to be generic enough, so introduction of new protocols which the server will be capable of speaking to, should be relatively straightforward.

Readme will be updated as more features will be added.
{'fraction_non_alphanumeric': 0.06286427976686094, 'fraction_numerical': 0.0033305578684429643, 'mean_word_length': 4.575406032482599, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, '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': '2690041', 'n_tokens_mistral': 612, 'n_tokens_neox': 587, 'n_words': 352}