<commit_before># ZQRPC: Protocol Buffer RPC transport

The idea is to create a mechanism for sending multiple requests if parallel and getting their answers
when needed. In between, the cclient thread is free to do its own work.
It is not necessary to fetch results in the same order as they have been submitted.

Please have a look at the examples folder.

## Usage

### Server
1. Start the context with n=1 string(s) and set up the server
<pre>
	context = new zmq::context_t(1);
	zqrpc::RpcServer rpc_server(context);<commit_msg>Tue Jul 29 11:37:02 IST 2014<commit_after># ZQRPC: Protocol Buffer RPC transport

The idea is to create a mechanism for sending multiple requests if parallel and getting their answers
when needed. In between, the client thread is free to do its own work.
It is not necessary to fetch results in the same order as they have been submitted.

Please have a look at the examples folder.

## Usage

### Server
1. Start the context with n=1 string(s) and set up the server
<pre>
	context = new zmq::context_t(1);
	zqrpc::RpcServer rpc_server(context);
{'fraction_non_alphanumeric': 0.06133828996282528, 'fraction_numerical': 0.016728624535315983, 'mean_word_length': 4.551546391752577, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, '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': '1287943', 'n_tokens_mistral': 315, 'n_tokens_neox': 301, 'n_words': 166}