[AMQCPP-457] Refactor Transports layer for more control over started / stopped state during initialization

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.6.0
• Component/s: Transports
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 07/Feb/13 17:30
• Updated: 02/May/13 02:30
• Resolved: 09/Feb/13 22:05

Description

Need to revisit the Transports layer and make the whole create / start / stop process more deterministic. The transports should do any connection logic until the filter chain is built and started as a whole, and once stopped no more async exceptions should come out.

The filter chain also needs to be modified to better deal with close and destroy. We need to ensure that the next Transport is held until destroy and that we walk down the chain and destroy the lowest one first before allowing high levels Transports to be destroyed.

Issue Links

• is depended upon by: AMQCPP-460 Access Violation