[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places
[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-635: -- Fix Version/s: (was: 0.9) Removing 0.9 fix-version since it doesn't seem like anything was done there. > PN_TRANSPORT events not generated in enough places > -- > > Key: PROTON-635 > URL: https://issues.apache.org/jira/browse/PROTON-635 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: 0.8 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > In writing a custom driver for Proton I noticed thatthe new events code does > not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol > header. > So a purely event driven driver is not going to send the outgoing protocol > header immediately, but is going to wait until it replies to the next frame > (open). > Also in error scenarios no PN_TRANSPORT is generated after the open/close > frames are generated. > This is going to end badly if the peer is waiting for the protocol header > before sending the open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places
[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-635: --- Fix Version/s: (was: 0.8) 0.9 PN_TRANSPORT events not generated in enough places -- Key: PROTON-635 URL: https://issues.apache.org/jira/browse/PROTON-635 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.8 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.9 In writing a custom driver for Proton I noticed thatthe new events code does not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol header. So a purely event driven driver is not going to send the outgoing protocol header immediately, but is going to wait until it replies to the next frame (open). Also in error scenarios no PN_TRANSPORT is generated after the open/close frames are generated. This is going to end badly if the peer is waiting for the protocol header before sending the open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places
[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-635: --- Summary: PN_TRANSPORT events not generated in enough places (was: PN_TRANSPORT event not genPN_TRANSPORT events not generated in enough placeserated after protocol header) PN_TRANSPORT events not generated in enough places -- Key: PROTON-635 URL: https://issues.apache.org/jira/browse/PROTON-635 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.8 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.8 In writing a custom driver for Proton I noticed thatthe new events code does not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol header. So a purely event driven driver is not going to send the outgoing protocol header immediately, but is going to wait until it replies to the next frame (open). This is going to end badly if the peer is waiting for the protocol header before sending the open. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (PROTON-635) PN_TRANSPORT events not generated in enough places
[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-635: --- Description: In writing a custom driver for Proton I noticed thatthe new events code does not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol header. So a purely event driven driver is not going to send the outgoing protocol header immediately, but is going to wait until it replies to the next frame (open). Also in error scenarios no PN_TRANSPORT is generated after the open/close frames are generated. This is going to end badly if the peer is waiting for the protocol header before sending the open. was: In writing a custom driver for Proton I noticed thatthe new events code does not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol header. So a purely event driven driver is not going to send the outgoing protocol header immediately, but is going to wait until it replies to the next frame (open). This is going to end badly if the peer is waiting for the protocol header before sending the open. PN_TRANSPORT events not generated in enough places -- Key: PROTON-635 URL: https://issues.apache.org/jira/browse/PROTON-635 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.8 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.8 In writing a custom driver for Proton I noticed thatthe new events code does not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol header. So a purely event driven driver is not going to send the outgoing protocol header immediately, but is going to wait until it replies to the next frame (open). Also in error scenarios no PN_TRANSPORT is generated after the open/close frames are generated. This is going to end badly if the peer is waiting for the protocol header before sending the open. -- This message was sent by Atlassian JIRA (v6.2#6252)
