I don't think it's worth retaining any JMS Client coding standards so I've removed the page.
I did however tweak the main coding standards [1] to briefly mention TODO comments, made a couple of draconian rules "recommended" rather than mandatory, and touched on documenting the thread-safety of classes. [1] https://cwiki.apache.org/confluence/display/qpid/Java+Coding+Standards On 5 June 2013 13:00, Gordon Sim <[email protected]> wrote: > On 06/05/2013 12:00 PM, Rafael Schloming wrote: > >> I think this approach is probably where we will end up going with proton >> with the further step of having the facade actually wrap a configurable >> logging callback so we don't need to build in any logging dependency at >> all >> and it becomes easy to integrate the engine's logging with the logging of >> its embedding application. >> > > This would be hugely beneficial for the c++ brokers use of proton. > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
