async client

[oroulet]

Client must ne ported to asio
-- to make subscription client work,
-- be portable to windows
-- to not hang if responses do not arrive in expected order

[arykovanov]

Refactored client code. Removed most of layers in client library: Now there will be one central component - BinaryServer. It will have a map of request handles and callback for processing responses in the same manner as in server OpcTcpMessages.
Algorithm will be the next:

1. Form Request.
2. Put into map <requestID, callback>.
3. Request is sent to server.
4. When response is came then corresponding requestID pops from map.
5. Deserialization and call callback.

[oroulet]

Sounds correct for me.

On 18 August 2014 09:47, Alexander Rykovanov notifications@github.com
wrote:

Refactored client code. Removed most of layers in client library: Now
there will be one central component - BinaryServer. It will have a set of
request handles and callback for processing responses in the same manner as
in server OpcTcpMessages.
Algorithm will be the next:

1. Form Request.
2. Put into map .
3. Request is sent to server.
4. When response is came then corresponding requestID pops from map.
5. Deserialization and call callback.

—
Reply to this email directly or view it on GitHub
#13 (comment).

[oroulet]

implemented