Pass RTS RPC commands from IN to OUT channel in RPC/Proxy

We use a custom RTS_CMD_CUSTOM_OUT to notify the connection close.

This RTS RPC commands are forwarded to the client except
for the previous custom one.
Return valid HTTP response when more data is needed
Implement naive flow control in IN channel for RPC/Proxy

This is required to make attachments sending work.

It sends a FlowControlAckWithDestination RTS RPC command
if the local available window is lower than the half of the window size.

This makes the sender to know it has room to send more PDUs.
Be more pep8 complaint

See https://www.python.org/dev/peps/pep-0008/ for details.
RTS cookies are transmitted using little endian

So we have to set it up the UUID objects properly
to use it in RTS RPC commands
Only RPC PDUs are subject to flow control

If all incoming data were treated as read, then the client
closes the connection as the data was inconsistent

   bytes_received > bytes_sent
Merge pull request #161 from sixstone-qq/ejhernandez/send-attachment-oa

Flow Control implementation in RPC over HTTP v2 server
Merge pull request #160 from exekias/fix_ntlm_auth_error

Return valid HTTP response when more data is needed
When provisioning send schemas additions to schema master
Merge pull request #149 from javierag/jag/provision-adc

Allow openchange provision in adc server
Merge branch 'master' of github.com:javierag/openchange