Relax client stream id constraints

• Convert to-client messages on closed streams to non-fatal to the overall connection. There is a time gap between the continuation removal on the client and the end-of-stream notice to the server

Crash fix and stream-id order fix

• Fixes an issue where a failed invocation of the on_incoming_stream callback in the server implementation would lead to a crash
• Fixes an issue where event stream ids could be submitted out-of-increasing-order to the server depending on what threads the continuation activation was invoked from.

Add function to to query port of server listener

What's Changed

• New: aws_event_stream_rpc_server_listener_get_bound_port() @graebm in #80

Full Changelog: v0.2.9...v0.2.10

Fix deprecated header encode API

• Fixes an issue (only present in v0.2.8) where the deprecated header write API (aws_event_stream_write_headers_to_buffer) would always fail

Security hardening and protocol error JSON fixes

• adds a significant amount of error-checking and safety-hardening
• fixes the JSON bodies of several protocol error messages

CONNECT_ACK bugfix

• Fix bug where client "forgets" it received CONNECT_ACK (#60)

Fix possible deadlock from on_closed callback

Release lock before invoking callbacks (#55)

Issue: We were seeing deadlock if one stream was activated from within the on_closed() callback of another stream. This was because we used a lock to protect continuation_table AND the on_closed() callback was automatically invoked when an entry was removed.

Solution is to remove the automatic action when entry removed from table. Instead we invoke the on_closed() callback after the lock is released.

Fixed gcc newline warning

v0.2.5

Added newline (#53)

Fixed shared lib build configuration

v0.2.4

Fixed shared-lib builds (#51)

Fixed shared lib test configuration

v0.2.3

Added test helper to ensure symbol is exported (#50)