From a really (really) quick glance at the source, I don’t think the BookPublisher code is handling dictionary requests itself. You can probably get ‘bookticker’ to work by using the same

Hi all, I'm testing the QPID bridge with bookpublisher and bookticker, but it seems that the dialog between them is stuck at the data dictionary request. This is the command lines: > bookpublisher -v

Thank you Damian, I don't want to bring it up just based on the code analysis. Let's see if I'd be able to come up with a test case that demonstrates different behaviour that is triggered by this

Hi all, Is this a valid MAMDA delete message, please (non-relevant fields

Hi all, Is this a valid MAMDA update message, please (non-relevant fields

Hey Dmitri, There's probably someone who can clarify better, but I believe the difference is the 'mNumEntries' is the total number of entries which the data feed has reported is part of the book, but

Hi, I'm working on a performance issue with the Solace proprietary OpenMAMA bridge processing MAMDA messages and I've come across this: void MamdaOrderBookPriceLevel::setNumEntries (mama_u32_t

Look good for Solace. Regards, Dmitri Fedorov Software Architect Solace Ottawa, ON Canada Solace Corporation accepts no liability for the content of thisemail, or for the consequences of any actions

Hi Dmitri. Honestly you should have reviewed it by now. The RFC review period is supposed to be 2 weeks and it has been almost a month now so it remains closed. In saying that if you want to suggest

T ​hanks Frank, The two different recap messages are from the same subscription at different points in time. I've looked at updates coming it, they don't look like the recap messages at all. None of

Hi Frank, can I have one more week for that please? Regards, Dmitri Fedorov Software Architect Solace Ottawa, ON Canada Solace Corporation accepts no liability for the content of thisemail, or for the

Hi Folks, As there have been no changes requested for this RFC, I will now consider it closed and approved. Thank you all for your attention in reviewing this. Cheers, Frank

Hi Dmitri, Best place to start would be for the updates coming in. Odds are you'll find these fields are getting populated from the data source containing each delta rather than from within MAMDA

Hi all, I'm investigating an issue in a Solace proprietary product that uses an instance of MamdaOrderBookListener to keep track of orders and to populate recap messages. During the investigation I've

Returning an error sounds fine to me. From: Frank Quinn [mailto:fquinn@...] Sent: 14 December 2016 09:24 To: Tom Doust <tom.doust@...>; Alpert, Reed <reed.alpert@...>; 'Openmama-dev@...'

Good question… the approach we had planned on taking was to allow accessors to be called and return an error if an extended value was requested via a function which doesn’t support extended

One question, (and I haven’t fully thought this through), is there any need to be able to determine at runtime, given a mamaDateTime object, whether it contains an extended value? Tom

Hi, This looks good for JPMChase, we will be able to support our securities before 1970 and far into the future. Thanks, Reed. From: openmama-dev-bounces@...

Hi Folks, I have just opened up a new RFC to cover the upcoming Extended MAMA Date Time functionality. You can find it listed here: https://openmama.github.io/openmama_rfc_open.html Also

Hi Folks, As hinted at during a recent email around the launch of the OpenMAMA Technical Documentation website, we now have a dedicated area on the site specifically for RFCs which includes ported