|
Re: Code change(s) just landed on origin/next (Successful)
Frank Quinn <f.quinn@...>
Hi Folks,
Please ignore these no changes notifications– this was just testing Jenkins integration with gitter (which is now working).
Cheers, Frank
From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...]
On Behalf Of jenkins@...
Sent: Wednesday, June 1, 2016 12:03 PM To: openmama-dev@... Subject: [Openmama-dev] Code change(s) just landed on origin/next (Successful)
Some changes have just been added to the origin/next branch! No changes Results for OpenMAMA Next Branch (Qpid Proton) CI run with latest changes:
You may also check CI console output to view the full results. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. SR Labs LLC
|
|
|
|
Code change(s) just landed on origin/next (Successful)
jenkins@...
Some changes have just been added to the origin/next branch!
No changes
Results for OpenMAMA Next Branch (Qpid Proton) CI run with latest changes:
You may also check CI console output to view the full results.
|
|
|
|
Code change(s) just landed on origin/next (Successful)
jenkins@...
Some changes have just been added to the origin/next branch!
No changes
Results for OpenMAMA Next Branch (Qpid Proton) CI run with latest changes:
You may also check CI console output to view the full results.
|
|
|
|
Re: subscribers notification to publishers
Frank Quinn <f.quinn@...>
Hi Dmitri,
Check out section 13.2 in this: http://www.openmama.org/sites/default/files/OpenMAMA%20Developer's%20Guide%20C.pdf and also table 12.
Also check out dqpublishermanager.h and capturereplay example apps for working examples.
Cheers, Frank
From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...]
On Behalf Of Dmitri Fedorov
Sent: Tuesday, May 31, 2016 10:43 PM To: openmama-dev <openmama-dev@...> Subject: [Openmama-dev] subscribers notification to publishers
Could you please point me in the code where I would be able to see what notifications and under what conditions are generated by OpenMAMA from subscribers to publishers?
Thank you in advance.
Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada
Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. SR Labs LLC
|
|
|
|
Re: fields MdSubscMsgType and MdMsgType in message
Frank Quinn <fquinn.ni@...>
Hi Dmitri, Where are you seeing this message? This will be driven by the data source, but MdSubscMsgType is typically only included in subscription request messages (as suggested in the comment in subscmsgtype.h). I wouldn't expect it to provide any relevant information when sent in an update (in fact it probably shouldn't be included in updates).
On Tue, May 31, 2016 at 10:27 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
|
|
|
|
Re: Gitter vs IRC
Damian Maguire <d.maguire@...>
Having toyed with it a bit, as well as many of the alternatives, I think Gitter is a really good option – public, easy to use for new users (beats IRC on that front), enough platform support for regular users to work with, preserves history (again beats IRC default), much more open than Slack etc. Integrations might need some work (CI notifications in the IRC channel are nice for example), but I think we can work around that.
So yeah, my vote is go for it (with some sort of plan for deprecating Freenode of course).
Cheers,
D
Damian Maguire Senior Sales Engineer Desk (Direct): +4428 9568 0298
From:
<openmama-dev-bounces@...> on behalf of Frank Quinn <fquinn.ni@...>
Hi folks,
You can already mess about in the proposed channel; you can read anonymously, or use a github or twitter account to contribute:
https://gitter.im/OpenMAMA/OpenMAMA The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. SR Labs LLC
|
|
|
|
subscribers notification to publishers
Dmitri Fedorov <dfedorov.solace@...>
Could you please point me in the code where I would be able to see what notifications and under what conditions are generated by OpenMAMA from subscribers to publishers? Thank you in advance. Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed in
writing. Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Solace Systems.
|
|
|
|
fields MdSubscMsgType and MdMsgType in message
Dmitri Fedorov <dfedorov.solace@...>
Hi, When a message has this field: MdSubscMsgType:61 and also it has this field: MdMsgType:1 am I right to assume that MdMsgType is the real message type? In other words, does MdMsgType take precedence over MdSubscMsgType? Do we have a legal/illegal combinations of MdMsgType and MdSubscMsgType? Thank you. Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed in
writing. Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Solace Systems.
|
|
|
|
Gitter vs IRC
Frank Quinn <fquinn.ni@...>
Hi folks,
We're currently looking at gitter as a potential IRC compatible replacement and my personal opinion is that we should go with it. You can already mess about in the proposed channel; you can read anonymously, or use a github or twitter account to contribute: https://gitter.im/OpenMAMA/OpenMAMA It has several great features: 1. Instant messages are persisted to the room, so you will see history when you log in 2. Sensible concurrent login access with no username1 nonsense 3. Web front end comes for free 4. Provided by github so integrates very nicely into the project wiki etc 5. Native client provided for Mac, windows, Linux, iPhone and android 6. Also compatible with standard IRC clients Downsides: 1. It increases the github lock-in 2. You'll need a github or twitter account to contribute If anyone has any feedback about making the move, please speak up now. I'm sending this to both users and developers because it will impact both and I'll welcome and consider all responses. I'd hope that we can agree a decision one way or another by 7th June, then (if necessary) take the plunge. Cheers, Frank
|
|
|
|
Re: Reference guide for data.dict file
Frank Quinn <fquinn.ni@...>
Hi Nestor, We would recommend following the Open Market Data Model - you should be able to find the original docs still hosted under NYSE: http://www.nyxdata.com/nysedata/Default.aspx?tabid=1211 Cheers,
On Thu, 19 May 2016, 21:01 Macrux, <kmacrux@...> wrote:
|
|
|
|
Reference guide for data.dict file
macrux
Hi there, Does anyone know if there is any reference guide for the contents of the dictionary included in the data.dict file. I would like to know what fields should I use if I want to send an order to broker (in fact, to a topic where a market gateway is listening to), for example.
|
|
|
|
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
see proton-c\include\proton\import_export.h, looks like PN_EXTERN gets resolved to __declspec(dllimport) Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed in
writing. Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Solace Systems.
On 17 May 2016 at 17:36, Dmitri Fedorov <dfedorov.solace@...> wrote:
|
|
|
|
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
0.12.1 Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed in
writing. Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Solace Systems.
On 17 May 2016 at 17:23, Frank Quinn <fquinn.ni@...> wrote:
|
|
|
|
Re: question about building on Windows
Frank Quinn <fquinn.ni@...>
That's a new one on me - I didn't need to specify any additional macros when I was building proton what version is this?
On Tue, 17 May 2016, 22:19 Dmitri Fedorov, <dfedorov.solace@...> wrote:
|
|
|
|
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
qpid-proton.dll I built doesn't have symbols from codec.h exported, so it look s like I'm missing qpid_proton_EXPORTS define, does it make sense? Thanks Dmitri Regards, Dmitri Fedorov Software Architect Solace Systems, Inc. Ottawa, ON Canada Solace Systems accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed in
writing. Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Solace Systems.
On 10 May 2016 at 09:37, Frank Quinn <fquinn.ni@...> wrote:
|
|
|
|
Java JNI programs not exiting
Alpert, Reed <reed.alpert@...>
Hi,
Our OpenMAMA Java programs do not exit due to remaining non-daemon threads from the OM JNI. Even if these native threads have exited the Java threads are still alive and prevent the JVM from exiting. I tried using AttachCurrentThreadAsDaemon() in mamajniutils.c and this solves the problem, allowing the JVM to exit.
Have other OM users seen the same thing? I want to make sure this is the issue rather than another problem with our Java apps.
Thanks,
Reed.
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.
|
|
|
|
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
Thanks Frank, sounds good Cheers Dmitri
On 11 May 2016 at 09:56, Frank Quinn <fquinn.ni@...> wrote:
|
|
|
|
Re: question about building on Windows
Frank Quinn <fquinn.ni@...>
Hi Dmitri, wiki.openmama.org is soon to be decommissioned, though I turned on write access for the OpenMAMA github wiki this morning if you want to start there?
On Wed, May 11, 2016 at 2:48 PM, Dmitri Fedorov <dfedorov.solace@...> wrote:
|
|
|
|
Re: question about building on Windows
Dmitri Fedorov <dfedorov.solace@...>
Hi Damian, For me the problem was in OpenMAMA, specifically, it was absence of clear and precise description of dependences: what's for the dependency is used, what versions for each platform and where from it gets retrieved for continuous integration. If you guys think it's worth having, then please give me credentials for http://wiki.openmama.org/ I could start making such table. Cheers Dmitri
On 11 May 2016 at 07:59, Damian Maguire <d.maguire@...> wrote:
|
|
|
|
Re: question about building on Windows
Damian Maguire <d.maguire@...>
For what it’s worth, I agree with Frank’s take here. I was looking at some of Dmitri’s questions last night and had to modify my own test environment to be able to recreate some of them – there’s clearly just too many factors for a project like ours to handle sensibly.
A side note on this – where we’re having to do something particularly unusual (such as copying header files around, or modifying includes), it might be beneficial for us to take the time to understand why. If it’s a problem with the way we use the libraries, that should probably be something we fix in OpenMAMA; If it’s a problem with the third party, we should probably see if we can either commit a fix upstream to the projects themselves, or at least raise a bug with them to see if it can be resolved (something we can point to the next time someone asks). Making our own changes and hiding them away is probably not the spirit of open source collaboration we’re going for.
Cheers,
D
Damian Maguire, Senior Sales Engineer Mobile: +44 7835 844 770 Desk (Direct): +4428 9568 0298 Adelaide Exchange | 24-26 Adelaide Street | Belfast | UK | BT2 8GD
SR.LABS Proven High Speed Electronic Trading Solutions
From:
<openmama-dev-bounces@...> on behalf of Dmitri Fedorov <dfedorov.solace@...>
Hi Frank,
This approach makes sense to me because my goal from the beginning was to assign proper values to EVENT_HOME, PROTON_HOME and AVIS_HOME.
Here is a branch I fixed to build with VS2015, I did not try it on other platforms (and I won't):
I'm not done yet :-)
Cheers Dmitri
Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.
On 10 May 2016 at 16:50, Frank Quinn <fquinn.ni@...> wrote:
The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. SR Labs LLC
|
|
|
