quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Marcin G. <mar...@ar...>]

Andrew Culross pisze:

Hi,

Speaking as local Polish programming company I'd also like to have a
chance to send some patches we've done for 1.12.4 C++ mainly (64bit/new
gcc/logs/Postgresql related/etc). If possible we can also offer our help
in developing new features into QuickFix.

Thanks,
Marcin


> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Some thoughts.
>
> 1. Latest integration of bug fixes into primary build
> 2. Little stuff that seems to be on the list frequently (rolling log files,
> encryption support)
> 3. Support for latest FIX releases (FastFIX, FIX5.0)
>
> Andrew Culross
> Direct   +1 (914) 220-8849 
> http://www.twofour.com/emaildisclaimer.aspx
>
> -----Original Message-----
> From: Chuck Remes [mailto:cre...@ma...] 
> Sent: Monday, March 09, 2009 12:09 PM
> To: or...@qu...
> Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy'
> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
>
>
> On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:
>
>   
>> Hold on guys.  We are still alive over here.  I know that's it's  
>> been a
>> while and I've neglected things for a bit.  I really would like to  
>> avoid
>> a fork, that would be messy.  I think we need to talk about what the
>> core issues that need to be addressed with the project and move  
>> forward
>> from there.
>>
>> --oren
>>     
>
> Oren,
>
> I'll take a first stab at listing a few things that I think are  
> important to this list. Hopefully others will chime in.
>
> 1. A release that builds cleanly under 64-bit OS.
>
> 2. A release that builds cleanly on Debian, FreeBSD and OSX. These  
> build issues *may* be related to gcc 4.3.x. Past emails to this list  
> indicate there may have been patches submitted for these issues.
>
> 3. Some members of this list may deserve commit rights. A move from  
> svn to git may streamline this a bit if you prefer to avoid giving  
> "strangers" commit rights to the svn repository. With git, everyone's  
> local repository is effectively a fork that can submit patches upstream.
>
> cr
>
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>   

[Quickfix-developers] Negotiated Deal Query

[Parag T. <tri...@gm...>]

Hello,
I have a query about Negotiated Deal implementation in FIX protocol 4.2. In
Negotiated Deal it is necessary to specifiy counter party Broker information
in order request. I want to know about a Tag No. which can be used to
specify counter party Broker Information.

Thanks in advance.

Regards,
Parag Trivedi

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Alexey Z. <ale...@in...>]

The bug tracker must be fixed first. There are a lot of stuff and we 
need to put it together.


Peter Piper wrote:
> Dear Oren,
>
> My immediate vote (apart from the bug fixes, of course) is to have:
>
> 1. Separate target directories for different compiler versions. I have 
> different active projects that use three versions of the Visual Studio 
> compiler (7, 8 and 9), for example. The raw distribution gets horribly 
> confused when all output directories are the same, so I have to hack 
> the makefiles a lot to make everything live happily in its own space. 
> I don;t want to have to repeat this process on every new release.
>
> 2. Add more robust versioning with build numbers, so that I can 
> distinguish bug fix releases from ones that might change the defined 
> behaviour (and therefore need a whole new folder tree). This probably 
> won't mix too well if you are going to allow others to commit but I'd 
> like to have some sort of idea of exactly which version is in the repo 
> whenever I do a clean download.
>
> Yours,
>
> Dan
>
> > From: And...@Tw...
> > To: cre...@ma...; or...@qu...
> > Date: Mon, 9 Mar 2009 12:16:17 -0400
> > CC: mke...@di...; 
> qui...@li...
> > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
> >
> > QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> > QuickFIX Support: http://www.quickfixengine.org/services.html
> >
> > Some thoughts.
> >
> > 1. Latest integration of bug fixes into primary build
> > 2. Little stuff that seems to be on the list frequently (rolling log 
> files,
> > encryption support)
> > 3. Support for latest FIX releases (FastFIX, FIX5.0)
> >
> > Andrew Culross
> > Direct +1 (914) 220-8849
> > http://www.twofour.com/emaildisclaimer.aspx
> >
> > -----Original Message-----
> > From: Chuck Remes [mailto:cre...@ma...]
> > Sent: Monday, March 09, 2009 12:09 PM
> > To: or...@qu...
> > Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy'
> > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
> >
> >
> > On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:
> >
> > > Hold on guys. We are still alive over here. I know that's it's
> > > been a
> > > while and I've neglected things for a bit. I really would like to
> > > avoid
> > > a fork, that would be messy. I think we need to talk about what the
> > > core issues that need to be addressed with the project and move
> > > forward
> > > from there.
> > >
> > > --oren
> >
> > Oren,
> >
> > I'll take a first stab at listing a few things that I think are
> > important to this list. Hopefully others will chime in.
> >
> > 1. A release that builds cleanly under 64-bit OS.
> >
> > 2. A release that builds cleanly on Debian, FreeBSD and OSX. These
> > build issues *may* be related to gcc 4.3.x. Past emails to this list
> > indicate there may have been patches submitted for these issues.
> >
> > 3. Some members of this list may deserve commit rights. A move from
> > svn to git may streamline this a bit if you prefer to avoid giving
> > "strangers" commit rights to the svn repository. With git, everyone's
> > local repository is effectively a fork that can submit patches upstream.
> >
> > cr
> >
> >
> >
> >
> > 
> ------------------------------------------------------------------------------
> > Open Source Business Conference (OSBC), March 24-25, 2009, San 
> Francisco, CA
> > -OSBC tackles the biggest issue in open source: Open Sourcing the 
> Enterprise
> > -Strategies to boost innovation and cut costs with open source 
> participation
> > -Receive a $600 discount off the registration fee with the source 
> code: SFAD
> > http://p.sf.net/sfu/XcvMzF8H
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> > https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
> ------------------------------------------------------------------------
> Share your photos with Windows Live Photos – Free. Try it Now! 
> <http://clk.atdmt.com/UKM/go/134665338/direct/01/>

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Mark T. K. <mke...@di...>]

oren, you need to open things up a bit.  you need an (unhackable :-) issue/bug tracking
system.  and you need to open up the repository to other developers.

/mark

Peter Piper wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>
> ------------------------------------------------------------------------
>
> Dear Oren,
>
> My immediate vote (apart from the bug fixes, of course) is to have:
>
> 1. Separate target directories for different compiler versions. I have
> different active projects that use three versions of the Visual Studio
> compiler (7, 8 and 9), for example. The raw distribution gets horribly
> confused when all output directories are the same, so I have to hack the
> makefiles a lot to make everything live happily in its own space. I
> don;t want to have to repeat this process on every new release.
>
> 2. Add more robust versioning with build numbers, so that I can
> distinguish bug fix releases from ones that might change the defined
> behaviour (and therefore need a whole new folder tree). This probably
> won't mix too well if you are going to allow others to commit but I'd
> like to have some sort of idea of exactly which version is in the repo
> whenever I do a clean download.
>
> Yours,
>
> Dan
>
>> From: And...@Tw...
>> To: cre...@ma...; or...@qu...
>> Date: Mon, 9 Mar 2009 12:16:17 -0400
>> CC: mke...@di...; qui...@li...
>> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
>>
>> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>> Some thoughts.
>>
>> 1. Latest integration of bug fixes into primary build
>> 2. Little stuff that seems to be on the list frequently (rolling log
> files,
>> encryption support)
>> 3. Support for latest FIX releases (FastFIX, FIX5.0)
>>
>> Andrew Culross
>> Direct +1 (914) 220-8849
>> http://www.twofour.com/emaildisclaimer.aspx
>>
>> -----Original Message-----
>> From: Chuck Remes [mailto:cre...@ma...]
>> Sent: Monday, March 09, 2009 12:09 PM
>> To: or...@qu...
>> Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy'
>> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
>>
>>
>> On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:
>>
>> > Hold on guys. We are still alive over here. I know that's it's
>> > been a
>> > while and I've neglected things for a bit. I really would like to
>> > avoid
>> > a fork, that would be messy. I think we need to talk about what the
>> > core issues that need to be addressed with the project and move
>> > forward
>> > from there.
>> >
>> > --oren
>>
>> Oren,
>>
>> I'll take a first stab at listing a few things that I think are
>> important to this list. Hopefully others will chime in.
>>
>> 1. A release that builds cleanly under 64-bit OS.
>>
>> 2. A release that builds cleanly on Debian, FreeBSD and OSX. These
>> build issues *may* be related to gcc 4.3.x. Past emails to this list
>> indicate there may have been patches submitted for these issues.
>>
>> 3. Some members of this list may deserve commit rights. A move from
>> svn to git may streamline this a bit if you prefer to avoid giving
>> "strangers" commit rights to the svn repository. With git, everyone's
>> local repository is effectively a fork that can submit patches upstream.
>>
>> cr
>>
>>
>>
>>
>>
> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
>> -Strategies to boost innovation and cut costs with open source
> participation
>> -Receive a $600 discount off the registration fee with the source
> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
> ------------------------------------------------------------------------
> Share your photos with Windows Live Photos – Free. Try it Now!
> <http://clk.atdmt.com/UKM/go/134665338/direct/01/>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers


This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Peter P. <pet...@ho...>]

Dear Oren,

My immediate vote (apart from the bug fixes, of course) is to have:

1. Separate target directories for different compiler versions. I have different active projects that use three versions of the Visual Studio compiler (7, 8 and 9), for example. The raw distribution gets horribly confused when all output directories are the same, so I have to hack the makefiles a lot to make everything live happily in its own space. I don;t want to have to repeat this process on every new release.

2. Add more robust versioning with build numbers, so that I can distinguish bug fix releases from ones that might change the defined behaviour (and therefore need a whole new folder tree). This probably won't mix too well if you are going to allow others to commit but I'd like to have some sort of idea of exactly which version is in the repo whenever I do a clean download.

Yours,

Dan

> From: And...@Tw...
> To: cre...@ma...; or...@qu...
> Date: Mon, 9 Mar 2009 12:16:17 -0400
> CC: mke...@di...; qui...@li...
> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> Some thoughts.
> 
> 1. Latest integration of bug fixes into primary build
> 2. Little stuff that seems to be on the list frequently (rolling log files,
> encryption support)
> 3. Support for latest FIX releases (FastFIX, FIX5.0)
> 
> Andrew Culross
> Direct   +1 (914) 220-8849 
> http://www.twofour.com/emaildisclaimer.aspx
> 
> -----Original Message-----
> From: Chuck Remes [mailto:cre...@ma...] 
> Sent: Monday, March 09, 2009 12:09 PM
> To: or...@qu...
> Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy'
> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
> 
> 
> On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:
> 
> > Hold on guys.  We are still alive over here.  I know that's it's  
> > been a
> > while and I've neglected things for a bit.  I really would like to  
> > avoid
> > a fork, that would be messy.  I think we need to talk about what the
> > core issues that need to be addressed with the project and move  
> > forward
> > from there.
> >
> > --oren
> 
> Oren,
> 
> I'll take a first stab at listing a few things that I think are  
> important to this list. Hopefully others will chime in.
> 
> 1. A release that builds cleanly under 64-bit OS.
> 
> 2. A release that builds cleanly on Debian, FreeBSD and OSX. These  
> build issues *may* be related to gcc 4.3.x. Past emails to this list  
> indicate there may have been patches submitted for these issues.
> 
> 3. Some members of this list may deserve commit rights. A move from  
> svn to git may streamline this a bit if you prefer to avoid giving  
> "strangers" commit rights to the svn repository. With git, everyone's  
> local repository is effectively a fork that can submit patches upstream.
> 
> cr
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

_________________________________________________________________
 25GB of FREE Online Storage – Find out more
http://clk.atdmt.com/UKM/go/134665320/direct/01/

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Andrew C. <And...@Tw...>]

Some thoughts.

1. Latest integration of bug fixes into primary build
2. Little stuff that seems to be on the list frequently (rolling log files,
encryption support)
3. Support for latest FIX releases (FastFIX, FIX5.0)

Andrew Culross
Direct   +1 (914) 220-8849 
http://www.twofour.com/emaildisclaimer.aspx

-----Original Message-----
From: Chuck Remes [mailto:cre...@ma...] 
Sent: Monday, March 09, 2009 12:09 PM
To: or...@qu...
Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy'
Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans


On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:

> Hold on guys.  We are still alive over here.  I know that's it's  
> been a
> while and I've neglected things for a bit.  I really would like to  
> avoid
> a fork, that would be messy.  I think we need to talk about what the
> core issues that need to be addressed with the project and move  
> forward
> from there.
>
> --oren

Oren,

I'll take a first stab at listing a few things that I think are  
important to this list. Hopefully others will chime in.

1. A release that builds cleanly under 64-bit OS.

2. A release that builds cleanly on Debian, FreeBSD and OSX. These  
build issues *may* be related to gcc 4.3.x. Past emails to this list  
indicate there may have been patches submitted for these issues.

3. Some members of this list may deserve commit rights. A move from  
svn to git may streamline this a bit if you prefer to avoid giving  
"strangers" commit rights to the svn repository. With git, everyone's  
local repository is effectively a fork that can submit patches upstream.

cr

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Chuck R. <cre...@ma...>]

On Mar 6, 2009, at 12:47 PM, or...@qu... wrote:

> Hold on guys.  We are still alive over here.  I know that's it's  
> been a
> while and I've neglected things for a bit.  I really would like to  
> avoid
> a fork, that would be messy.  I think we need to talk about what the
> core issues that need to be addressed with the project and move  
> forward
> from there.
>
> --oren

Oren,

I'll take a first stab at listing a few things that I think are  
important to this list. Hopefully others will chime in.

1. A release that builds cleanly under 64-bit OS.

2. A release that builds cleanly on Debian, FreeBSD and OSX. These  
build issues *may* be related to gcc 4.3.x. Past emails to this list  
indicate there may have been patches submitted for these issues.

3. Some members of this list may deserve commit rights. A move from  
svn to git may streamline this a bit if you prefer to avoid giving  
"strangers" commit rights to the svn repository. With git, everyone's  
local repository is effectively a fork that can submit patches upstream.

cr

[Quickfix-developers] Quickfix python configuration

[Jason B. <jas...@ma...>]

Hi All I would like to test quickfix with python.  However the
quickfix.py file will not run as it complains: import _quickfix

ImportError: No module named _quickfix

I ssume that this is becuase it can not find _quickfix.pyd.  I see this
is not in the compiled release and that it is necessary to compile
QuickfixPython.cpp to create it.

However I find this will not compile on Visual Studio as it can not find
the config.h file.  If I create the config.h containing for example

#define HAVE_MSSQL 1

The project will still not install, having many errors such as:

error C2440: 'initializing' : cannot convert from 'const char *' to 'char
*'

If I try and use the automake in Cygwin it syas can not find
configuation.in for example.

Does anyone have a precompiled ~_quickfix.pyd or are there any documents
on how to create it assuming my assumptions above are correct.

Jason


-- Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com!
-- Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com!

-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[<or...@qu...>]

Hold on guys.  We are still alive over here.  I know that's it's been a
while and I've neglected things for a bit.  I really would like to avoid
a fork, that would be messy.  I think we need to talk about what the
core issues that need to be addressed with the project and move forward
from there.

--oren

> -------- Original Message --------
> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release
> plans
> From: "Andrew Culross" <And...@Tw...>
> Date: Fri, March 06, 2009 11:15 am
> To: "'Mark T. Kennedy'" <mke...@di...>, "'Chuck Remes'"
> <cre...@ma...>
> Cc: 'quickfix developers' <qui...@li...>
> 
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> I'm wondering if the core developers have just moved over to the QuickFIX/J
> implementation - seems like there is a little more going on over there . . .
> 
> But yeah, I'd like to know if this is a dead-end as well.
> 
> Andrew Culross
> Direct   +1 (914) 220-8849 
> http://www.twofour.com/emaildisclaimer.aspx
> 
> -----Original Message-----
> From: Mark T. Kennedy [mailto:mke...@di...] 
> Sent: Friday, March 06, 2009 11:33 AM
> To: Chuck Remes
> Cc: quickfix developers
> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans
> 
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> 
> uh oh - the "f" word :-).  but you may be right.  drew et al, can you shed
> some light on things?
> /mark
> 
> Chuck Remes wrote:
> > On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote:
> > 
> >> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> >> QuickFIX Support: http://www.quickfixengine.org/services.html
> >>
> >>
> >> the www.quickfixengine.org web site still points at the "Hacked by  
> >> the Hunter" bug tracking page.
> >> no replacement has been forthcoming.  nor have the bugs that i found  
> >> and fixed in 12.4, which
> >> lead to the loss of messages and a blocked runtime, made it into any  
> >> release.
> >>
> >> can someone post a status message?  what are the plans of the  
> >> primary developers?
> > 
> > Two or three times a month there is a post to this list asking about  
> > new releases, getting bug fixes submitted and pulled into trunk, etc.  
> > There are rarely any responses from the core devs. The last release is  
> > going on 3 years ago.
> > 
> > Time to fork.
> > 
> > cr
> > 
> > 
> 
> This communication and any attachments may contain confidential/proprietary
> information and is intended for information purposes only. It is not an
> invitation or offer to purchase interests from Diamondback.  Any
> representation to the contrary is unintentional.  This communication is
> intended only for the person(s) to whom it is addressed.  If you are not the
> intended recipient you are hereby notified that you have received this
> document in error and that any review, dissemination, distribution, or
> copying of this message or any attachments is not permitted.  If you have
> received this in error, please notify the sender immediately by e-mail and
> delete this message.  All e-mails sent to or received from this address will
> be received by Diamondback's company e-mail system and is subject to
> archival and possible review by someone other than the recipient.  This
> notice is automatically appended to each e-mail message leaving Diamondback.
> 
> 
> ----------------------------------------------------------------------------
> --
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] Fwd: Problems with MarketDataIncrementalRefresh

[Andre D. <and...@al...>]

Hi All,

I'm new with quickfix, but I'm creating a application to read a text file
with FIX lines.
I use the Parser class to validate the message and it's OK.

-------------------------------------
8=FIX.4.4 9=628 35=X 34=2 49=TradingEngineDerivatives01A
52=20080501-03:35:23.379 56=FIXGatewayDerivatives_MD 10016=15977_1
75=20080501 268=5 279=1 269=c 278=1 55=BGIJ09 48=BMFBR7312910 22=8
272=20080501 273=03:35:10 336=TradingSessionID 326=122 279=2 269=d 278=2
55=BGIJ09 48=BMFBR7312910 22=8 272=20080501 273=03:35:10
336=TradingSessionID 279=1 269=b 278=3 55=BGIJ09 48=BMFBR7312910 22=8
272=20080501 273=03:35:10 336=TradingSessionID 625=I 279=1 269=c 278=4
55=BGIJ09 48=BMFBR7312910 22=8 272=20080501 273=03:35:10
336=TradingSessionID 326=122 279=2 269=d 278=5 55=BGIJ09 48=BMFBR7312910
22=8 272=20080501 273=03:35:10 336=TradingSessionID 10=034

8=FIX.4.4 9=630 35=X 34=3 49=TradingEngineDerivatives01A
52=20080501-03:35:23.395 56=FIXGatewayDerivatives_MD 10016=14827_105
75=20080501 268=5 279=1 269=c 278=1 55=BGIH09 48=BMFBR7312795 22=8
272=20080501 273=03:35:10 336=TradingSessionID 326=122 279=2 269=d 278=2
55=BGIH09 48=BMFBR7312795 22=8 272=20080501 273=03:35:10
336=TradingSessionID 279=1 269=b 278=3 55=BGIH09 48=BMFBR7312795 22=8
272=20080501 273=03:35:10 336=TradingSessionID 625=I 279=1 269=c 278=4
55=BGIH09 48=BMFBR7312795 22=8 272=20080501 273=03:35:10
336=TradingSessionID 326=122 279=2 269=d 278=5 55=BGIH09 48=BMFBR7312795
22=8 272=20080501 273=03:35:10 336=TradingSessionID 10=165
-------------------------------------

But when I send to the MessageCracker I have problems.

When I try to get the NoMDEntries group I got an error: FieldNotFound.

-------------------------------------
  // Test if we have the groups
  FIX44::MarketDataIncrementalRefresh::NoMDEntries noMDEntriesGroup;
  if( !message.hasGroup( noMDEntriesGroup ) )
  {
    std::cout << "\n\tInvalid Message: no Group\n]\n";
    return;
  }

  // Read a entry group
  try
  {
    message.getGroup( 1, noMDEntriesGroup );
  }
  catch( FIX::FieldNotFound e )
  {
    std::cout << "\tnoGroup(" << e.field << ")";
    continue;
  }
-------------------------------------

Investigating the problem, I try to use the DataDictinary to validate the
message:

-------------------------------------
DD_FIX44 = new FIX::DataDictionary( "/opt/quickfix/share/quickfix/FIX44.xml"
);

  try
  {
    const std::string& msgTypeValue = message.getHeader().getField(
FIX::FIELD::MsgType );
    std::string str;
    DD_FIX44->getFieldName( 22, str );
    std::cout << "[ " << str << " ] "
              << msgTypeValue << "  "
              << DD_FIX44->isMsgField( msgTypeValue, 22 ) << std::endl;

    DD_FIX44->validate( message );
  }
  catch( FIX::TagNotDefinedForMessage e )
  {
    std::cout << "Problems: [ TagNotDefinedForMessage " << e.field <<
e.detail
              << " ]" << std::endl;
  }

OUTPUT:
[ SecurityIDSource ] X  0
Problems: [ TagNotDefinedForMessage 22 ]

-------------------------------------

The problem is: the tag 22 (SecurityIDSource), present in the FIX messages,
is return that is NOT defined for the message.
But looking at the XML and the "fix44/MarketDataIncrementalRefresh.h" is
defined!

So, any one with this problem? Any help?

Thanks in advance,
Andre B Derraik.
ALBD Consulting

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Andrew C. <And...@Tw...>]

I'm wondering if the core developers have just moved over to the QuickFIX/J
implementation - seems like there is a little more going on over there . . .

But yeah, I'd like to know if this is a dead-end as well.

Andrew Culross
Direct   +1 (914) 220-8849 
http://www.twofour.com/emaildisclaimer.aspx

-----Original Message-----
From: Mark T. Kennedy [mailto:mke...@di...] 
Sent: Friday, March 06, 2009 11:33 AM
To: Chuck Remes
Cc: quickfix developers
Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html


uh oh - the "f" word :-).  but you may be right.  drew et al, can you shed
some light on things?
/mark

Chuck Remes wrote:
> On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote:
> 
>> QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>> the www.quickfixengine.org web site still points at the "Hacked by  
>> the Hunter" bug tracking page.
>> no replacement has been forthcoming.  nor have the bugs that i found  
>> and fixed in 12.4, which
>> lead to the loss of messages and a blocked runtime, made it into any  
>> release.
>>
>> can someone post a status message?  what are the plans of the  
>> primary developers?
> 
> Two or three times a month there is a post to this list asking about  
> new releases, getting bug fixes submitted and pulled into trunk, etc.  
> There are rarely any responses from the core devs. The last release is  
> going on 3 years ago.
> 
> Time to fork.
> 
> cr
> 
> 

This communication and any attachments may contain confidential/proprietary
information and is intended for information purposes only. It is not an
invitation or offer to purchase interests from Diamondback.  Any
representation to the contrary is unintentional.  This communication is
intended only for the person(s) to whom it is addressed.  If you are not the
intended recipient you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or
copying of this message or any attachments is not permitted.  If you have
received this in error, please notify the sender immediately by e-mail and
delete this message.  All e-mails sent to or received from this address will
be received by Diamondback's company e-mail system and is subject to
archival and possible review by someone other than the recipient.  This
notice is automatically appended to each e-mail message leaving Diamondback.


----------------------------------------------------------------------------
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Dale W. <wi...@oc...>]

I work for OCI.  (www.ociweb.com) Because it's been so long since there 
was a QuickFIX release, we have been supporting version of QuickFIX with 
enhancements -- including 64 bit builds and bug fixes)  for some of our 
customers.  We would be interested in helping with a fork if it becomes 
necessary.  I'm still hoping to hear from Oren and some of the other 
developers involved in the current QuickFIX project.

Dale Wilson
Principal Software Engineer
Object Computing, Inc.

Mark T. Kennedy wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> uh oh - the "f" word :-).  but you may be right.  drew et al, can you shed some light on things?
> /mark
>
> Chuck Remes wrote:
>   
>> On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote:
>>
>>     
>>> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
>>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>>
>>>
>>> the www.quickfixengine.org web site still points at the "Hacked by  
>>> the Hunter" bug tracking page.
>>> no replacement has been forthcoming.  nor have the bugs that i found  
>>> and fixed in 12.4, which
>>> lead to the loss of messages and a blocked runtime, made it into any  
>>> release.
>>>
>>> can someone post a status message?  what are the plans of the  
>>> primary developers?
>>>       
>> Two or three times a month there is a post to this list asking about  
>> new releases, getting bug fixes submitted and pulled into trunk, etc.  
>> There are rarely any responses from the core devs. The last release is  
>> going on 3 years ago.
>>
>> Time to fork.
>>
>> cr
>>
>>
>>     
>
> This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>   

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Mark T. K. <mke...@di...>]

uh oh - the "f" word :-).  but you may be right.  drew et al, can you shed some light on things?
/mark

Chuck Remes wrote:
> On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote:
> 
>> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>> the www.quickfixengine.org web site still points at the "Hacked by  
>> the Hunter" bug tracking page.
>> no replacement has been forthcoming.  nor have the bugs that i found  
>> and fixed in 12.4, which
>> lead to the loss of messages and a blocked runtime, made it into any  
>> release.
>>
>> can someone post a status message?  what are the plans of the  
>> primary developers?
> 
> Two or three times a month there is a post to this list asking about  
> new releases, getting bug fixes submitted and pulled into trunk, etc.  
> There are rarely any responses from the core devs. The last release is  
> going on 3 years ago.
> 
> Time to fork.
> 
> cr
> 
> 

This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.

Re: [Quickfix-developers] bugs, bug tracking, and release plans

[Chuck R. <cre...@ma...>]

On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> the www.quickfixengine.org web site still points at the "Hacked by  
> the Hunter" bug tracking page.
> no replacement has been forthcoming.  nor have the bugs that i found  
> and fixed in 12.4, which
> lead to the loss of messages and a blocked runtime, made it into any  
> release.
>
> can someone post a status message?  what are the plans of the  
> primary developers?

Two or three times a month there is a post to this list asking about  
new releases, getting bug fixes submitted and pulled into trunk, etc.  
There are rarely any responses from the core devs. The last release is  
going on 3 years ago.

Time to fork.

cr

[Quickfix-developers] bugs, bug tracking, and release plans

[Mark T. K. <mke...@di...>]

the www.quickfixengine.org web site still points at the "Hacked by the Hunter" bug tracking page.
no replacement has been forthcoming.  nor have the bugs that i found and fixed in 12.4, which
lead to the loss of messages and a blocked runtime, made it into any release.

can someone post a status message?  what are the plans of the primary developers?

/mark

This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.

Re: [Quickfix-developers] SocketAcceptor::onPoll()

[Peter P. <pet...@ho...>]

Dear Mark,

Sorry? What has this got to do with onPoll()?

Yours,

Dan

> Date: Wed, 4 Mar 2009 15:28:20 -0500
> From: mke...@di...
> CC: qui...@li...
> Subject: Re: [Quickfix-developers] SocketAcceptor::onPoll()
> 
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 

_________________________________________________________________
Free photo editing software from Windows Live . Try it now! 
http://clk.atdmt.com/UKM/go/134665240/direct/01/

Re: [Quickfix-developers] A Cup of Java and A QF biscuit... Beginner Questions

[Mike G. <mg...@co...>]

See also: http://www.quickfixj.org/

-- 
Mike Gatny
Connamara Systems, LLC
http://www.connamara.com/

Re: [Quickfix-developers] SocketAcceptor::onPoll()

[Mark T. K. <mke...@di...>]

just out of curiosity, do you see any of the code from the attached patch in your source
tree?  it fixes at least one deadlock problem.

/mark

Peter Piper wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Hi,
> 
> I'm investigating a deadlock somewhere in my application that uses
> Quickfix, so I am squirreling through the source looking for likely
> culprits. The onPoll() member seems oddly constructed to me (source
> copied below).
> 
> In particular:
> 
> 1. Why have the test for start = 0, as it will always be zero at that
> point? (Not going to ask why those variables declared outside the if()
> scope!)
> 
> 2. Why is start (an automatic and therefore local variable) reset to
> zero before the function returns and destroys it anyway?
> 
> I looked at an earlier copy of quickfix (also confusingly called version
> 1.12.4) and the start variable does not exist at all in that version, so
> I'm confused as to why it should have ended up looking this messy?
> 
> Anyone else think this is odd or am I having a bad hair day?
> 
> Yours,
> 
> Dan
> 
> ----- code from Subversion repository version 1.12.4 as of 11 FEB 2009 -----
> 
> bool SocketAcceptor::onPoll( double timeout )
> { QF_STACK_PUSH(SocketAcceptor::onPoll)
> 
>   if( !m_pServer )
>     return false;
> 
>   time_t start = 0;
>   time_t now = 0;
> 
>   if( isStopped() )
>   {
>     if( start == 0 )
>       ::time( &start );
>     if( !isLoggedOn() )
>     {
>       start = 0;
>       return false;
>     }
>     if( ::time(&now) - 5 >= start )
>     {
>       start = 0;
>       return false;
>     }
>   }
> 
>   m_pServer->block( *this, true, timeout );
>   return true;
> 
>   QF_STACK_POP
> }
> 
> 
> ------------------------------------------------------------------------
> Windows Live Hotmail just got better. Find out more!
> <http://clk.atdmt.com/UKM/go/134665311/direct/01/>
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers


This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.

[Quickfix-developers] SocketAcceptor::onPoll()

[Peter P. <pet...@ho...>]

Hi,

I'm investigating a deadlock somewhere in my application that uses Quickfix, so I am squirreling through the source looking for likely culprits. The onPoll() member seems oddly constructed to me (source copied below).

In particular:

1. Why have the test for start = 0, as it will always be zero at that point? (Not going to ask why those variables declared outside the if() scope!)

2. Why is start (an automatic and therefore local variable) reset to zero before the function returns and destroys it anyway?

I looked at an earlier copy of quickfix (also confusingly called version 1.12.4) and the start variable does not exist at all in that version, so I'm confused as to why it should have ended up looking this messy?

Anyone else think this is odd or am I having a bad hair day?

Yours,

Dan

----- code from Subversion repository version 1.12.4 as of 11 FEB 2009 -----

bool SocketAcceptor::onPoll( double timeout )
{ QF_STACK_PUSH(SocketAcceptor::onPoll)

  if( !m_pServer )
    return false;

  time_t start = 0;
  time_t now = 0;

  if( isStopped() )
  {
    if( start == 0 )
      ::time( &start );
    if( !isLoggedOn() )
    {
      start = 0;
      return false;
    }
    if( ::time(&now) - 5 >= start )
    {
      start = 0;
      return false;
    }
  }

  m_pServer->block( *this, true, timeout );
  return true;

  QF_STACK_POP
}


_________________________________________________________________
View your Twitter and Flickr updates from one place – Learn more!
http://clk.atdmt.com/UKM/go/137984870/direct/01/

Re: [Quickfix-developers] A Cup of Java and A QF biscuit... Beginner Questions

[Malinka R. <ael...@gm...>]

You can't use QF on Mono w/o a lot of work, QF is C++ and then Wrapper
layers are invented to work with the .NET or JNI, etc.  so basically
long story short you can't compile QF with mono to run in .NET in
linux, however you can use http://www.mono-project.com/Embedding_Mono
to make a C++ .NET bridge using mono, haven't tried that personally.
About the java problem there has to be an environment variable for
where jave looks for libraries and you would need to add
/usr/local/lib to that path, however I don't use java normally so I
don't know it offhand

On Wed, Mar 4, 2009 at 02:26, Neil Franken
<nfr...@th...> wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Hi All
>
>
>
> I am just starting with quickfix and Java. I am running Ubuntu 8.1 and using Netbeans 6.  I can import the quickfix.jar file and I have the quickfix object available. However I have a problem loading the library quickfixjni. It is stored in my /usr/local/lib path and it appears that the Java library path is pointing to (amongst others) /usr/lib. Now I am busy getting rid of my windows habit and this is my first time programming in *nix.
>
>
>
> So is there anyone on this list that can give me some pointers(not the C++) type on how to make sure that Java can see these librarie?. Sorry for such basic question I come from mainly a C++/Delphi background however my clients want to run on Windows so Java is the way for me at the moment.
>
>
>
> Just one other question has anyone tried using quickfix on Mono?
>
>
>
> Regards
>
> Neil
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

Re: [Quickfix-developers] Multiple Emails

[Grant B. <gbi...@co...>]

I'm only getting one of each, so it's not happening to everyone.


On Wed, Mar 4, 2009 at 7:31 AM, Brian Erst
<azz...@ya...> wrote:
> - Show quoted text -
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> I *wish* it was just 2-4 copies - it's been getting worse each day. Now I'm getting about 10-12 copies of each email. I got three more just while typing this message.
>
> ________________________________
> From: Mike Perik <mic...@ya...>
> To: qui...@li...
> Sent: Tuesday, March 3, 2009 9:21:26 PM
> Subject: [Quickfix-developers] Multiple Emails
>
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Is anyone else getting 2-4 copies of each email?
>
> Mike
>
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

Re: [Quickfix-developers] Multiple Emails

[Brian E. <azz...@ya...>]

I *wish* it was just 2-4 copies - it's been getting worse each day. Now I'm getting about 10-12 copies of each email. I got three more just while typing this message.




________________________________
From: Mike Perik <mic...@ya...>
To: qui...@li...
Sent: Tuesday, March 3, 2009 9:21:26 PM
Subject: [Quickfix-developers] Multiple Emails

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html


Is anyone else getting 2-4 copies of each email?

Mike


      

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] Rolling file log

[Alexander K. <ale...@un...>]

Hi Brian,

This sounds good! Could you publish your changes to the code? That would 
be great!

Thanks,
Alex

Brian Ho schrieb:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> I had to modify QuickFIX to add this functionality and make it
> configurable via the settings file.
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 20 Feb 2009 02:35:02 -0600
> From: Karsten Str?b?k <ks...@cf...>
> Subject: [Quickfix-developers] Rolling file log
> To: <qui...@li...>
> Message-ID:
> 	
> <7CD29711D8DF224395DAEA10C842BC05057E7C4B@34093-EVS2C2.exchange.rackspac
> e.com>
> 	
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> Does anyone know if it is possible to configure Quickfix to use rolling
> log files? I would be nice to have the "raw" fix messages for each day
> in a file of its own.
>
> Thank you.
>
> Karsten
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>   

[Quickfix-developers] A Cup of Java and A QF biscuit... Beginner Questions

[Neil F. <nfr...@th...>]

Hi All

 

I am just starting with quickfix and Java. I am running Ubuntu 8.1 and
using Netbeans 6.  I can import the quickfix.jar file and I have the
quickfix object available. However I have a problem loading the library
quickfixjni. It is stored in my /usr/local/lib path and it appears that
the Java library path is pointing to (amongst others) /usr/lib. Now I am
busy getting rid of my windows habit and this is my first time
programming in *nix.

 

So is there anyone on this list that can give me some pointers(not the
C++) type on how to make sure that Java can see these librarie?. Sorry
for such basic question I come from mainly a C++/Delphi background
however my clients want to run on Windows so Java is the way for me at
the moment.

 

Just one other question has anyone tried using quickfix on Mono?

 

Regards

Neil

[Quickfix-developers] Multiple Emails

[Mike P. <mic...@ya...>]

Is anyone else getting 2-4 copies of each email?

Mike