To clarify: For the behavior you propose to work, send() on a Datapath would have to return True or False - so as to communicate to the application that called send() that the particular call to send() succeeded or failed.
A failed send() (returning False) would indicate to the application that the Datapath was "stale," and that it should update its internal records. Making this happen is easy, if we wish; I simply need to add "return msg_enqueued" to the end of send(). This should not be application impacting; existing applications can continue to ignore the return code. We just need to decide if we want to expose a return code from send() at all - since, as soon as we do, the specter of potential user application breakage awakes, and we need to ensure that the behavior remains compatible going forward. Best, Victor -- Victor J. Orlikowski <> vjo@[cs.]duke.edu > On Mar 1, 2016, at 8:41 PM, Victor Orlikowski <[email protected]> wrote: > > As of today, send() on a Datapath does not return an error to the application > that calls it. > The behavior you describe would require that behavior. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
