Hi, Mark. We marked it internal and undocumented because we anticipated changing it to take an optional session_options argument, the same way that link.open takes link_options.
You should go ahead and use it in your wrapper, but with the awareness that you may have to change it. We did something similar with the constructor for handler, because we planned to move (and have moved) the options from there to sender and receiver options. In general, it's clear now that the API is going to see some more changes. We will publish a detailed list of the changes before we release 0.13. Whenever possible they will be backward-compatible additions. You can see the proposed shape of things in the working API spec. In some cases, the C++ implementation hasn't caught up with the spec yet. http://home.apache.org/~jross/pumpjack/core/session/index.html http://home.apache.org/~jross/pumpjack/core/session-options/index.html I've also updated the Proton master snapshot so you can see the current API doc. http://qpid.apache.org/releases/qpid-proton-master/proton/cpp/api/annotated.html Justin On Thu, Mar 24, 2016 at 2:39 AM, Mark Banner <[email protected]> wrote: > Hi all, > > We are writing a custom JMS-like wrapper over the proton-cpp API. In order > to open a session, I need to use the session::open method. This method is > exported in the public headers but is declared as internal and is not > available in the documentation. > > Should I avoiding using this method and open sessions another way? > > Mark >
