<commit_before>* add response to socket on critical error if has requestId

* client
	* body parsing options
	* headers translation options
	* think about moving errors extraction to some common area (lib, etc?)
	* fix *EventListener issues

* think about combining all apis headers into single http header - be careful, can have single row length issues
* make event names camelCase ? (check guidelines)
* make ids camelCase on test page

* make Loader command set easier to extend

## WARN

* extends http.IncomingMessage.prototype (just like express 2.X does)
* usage of undocumented res._headers (wrap setHeader, removeHeader instead?)
* JSONP has no origin-based restrictions, potential subject of distributed browser-based atacks (don't know good way to fix)
* no compression - add server.use(express.compress()); to mechanics/web after express migration to connect 2.X
* web mechanics performs req.pause() before call handler, so it may be reasonable to call resume() somewhere ('data' handler does it)

## test page

* move testPage to client/
* ability to copy/save/load requests

## batch

* review batches (possibly broken)
* add batches support to client library
* ability to fetch less data than used in 'apply' (?)
* optionally fail on error
<commit_msg>TODO updated<commit_after>* add response to socket on critical error if has requestId

* client
	* body parsing options
	* headers translation options
	* think about moving errors extraction to some common area (lib, etc?)
	* fix *EventListener issues

* think about combining all apis headers into single http header - be careful, can have single row length issues
* make event names camelCase ? (check guidelines)
* make ids camelCase on test page

* make Loader command set easier to extend

## browserify

* use -r path:dst when will be fixed (instead of client/expose/browserify.js)

## WARN

* extends http.IncomingMessage.prototype (just like express 2.X does)
* usage of undocumented res._headers (wrap setHeader, removeHeader instead?)
* JSONP has no origin-based restrictions, potential subject of distributed browser-based atacks (don't know good way to fix)
* no compression - add server.use(express.compress()); to mechanics/web after express migration to connect 2.X
* web mechanics performs req.pause() before call handler, so it may be reasonable to call resume() somewhere ('data' handler does it)

## test page

* move testPage to client/
* ability to copy/save/load requests

## batch

* review batches (possibly broken)
* add batches support to client library
* ability to fetch less data than used in 'apply' (?)
* optionally fail on error

{'fraction_non_alphanumeric': 0.06922784328642069, 'fraction_numerical': 0.0015214910612400153, 'mean_word_length': 4.607675906183369, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, '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': '687251', 'n_tokens_mistral': 681, 'n_tokens_neox': 651, 'n_words': 348}