Sha256: fde90edb4447269552dc703a523395842db7fe3cc97771e21ecd9275972239bf
Contents?: true
Size: 956 Bytes
Versions: 2
Compression:
Stored size: 956 Bytes
Contents
@open_flow10 Feature: Barrier::Request When the controller wants to ensure message dependencies have been met or wants to receive notifications for completed operations, it may use an Barrier Request message. This message has no body. Scenario: new When I create an OpenFlow message with: """ Pio::Barrier::Request.new """ Then the message has the following fields and values: | field | value | | version | 1 | | transaction_id | 0 | | xid | 0 | | body | | Scenario: new(transaction_id: 123) When I create an OpenFlow message with: """ Pio::Barrier::Request.new(transaction_id: 123) """ Then the message has the following fields and values: | field | value | | version | 1 | | transaction_id | 123 | | xid | 123 | | body | |
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
pio-0.30.2 | features/open_flow10/barrier_request.feature |
pio-0.30.1 | features/open_flow10/barrier_request.feature |