quickfix-developers Mailing List for QuickFIX (Page 85)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Take a look at the runpt* scripts in the test/ directory.

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

Does quickfix comes with a peformance test suite which can test the
performance of the engine?

I can see test suites for unit and acceptance testing however cannot spot
any performance test suites.

thanks,
-- Sibte

It is just looking for the QuickFIX shared object.  One of the things
the script does is setup the LD_LIBRARY_PATH for the executable.  If you
do a make install on your box, it would find the library fine.  Your
other options are to grab te executable and the library and setup
LD_LIBRARY_PATH yourself.  Or, you can build with the --disable-shared
--enable-static and the library should link everything directly into the
executable.  This should make transporting it easier.

--oren

> -------- Original Message --------
> Subject: [Quickfix-developers] building C++ tradeclient into an
> executable
> From: fopguy <ma...@tr...>
> Date: Fri, May 02, 2008 8:42 am
> To: qui...@li...
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> The makefile that comes with quickfix builds the C++ tradeclient into an
> executable and a script. I see that in the makefile, it is the libtool
> script that makes the tradeclient script inside the main directory, and a
> tradeclient executable inside .libs.
> I can invoke tradeclient with the script, but invoking the executable
> directly gives me a shared library error.
> $ cd .libs
> $./tradeclient tradeclient.cfg
> ./tradeclient: error while loading shared libraries: libquickfix.so.10:
> cannot open shared object file: No such file or directory
> I was wondering if anyone has experience modifying the build process so that
> it builds 
> 1) an executable only (no script)
> 2) portable to another machine. 
> I'm guessing that would require figuring out what exactly libtool does and
> condensing it into one g++ line.
> If anyone has information about that, I would deeply appreciate it.
> thanks
> mark
> -- 
> View this message in context: http://www.nabble.com/building-C%2B%2B-tradeclient-into-an-executable-tp17019718p17019718.html
> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

The makefile that comes with quickfix builds the C++ tradeclient into an
executable and a script. I see that in the makefile, it is the libtool
script that makes the tradeclient script inside the main directory, and a
tradeclient executable inside .libs.

I can invoke tradeclient with the script, but invoking the executable
directly gives me a shared library error.

$ cd .libs
$./tradeclient tradeclient.cfg

./tradeclient: error while loading shared libraries: libquickfix.so.10:
cannot open shared object file: No such file or directory

I was wondering if anyone has experience modifying the build process so that
it builds 
1) an executable only (no script)
2) portable to another machine. 

I'm guessing that would require figuring out what exactly libtool does and
condensing it into one g++ line.

If anyone has information about that, I would deeply appreciate it.

thanks

mark
-- 
View this message in context: http://www.nabble.com/building-C%2B%2B-tradeclient-into-an-executable-tp17019718p17019718.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Hi,

I was going through the example for Thomas Bakker code; I do not
understand how we can call Send method in this example that is from
toApp.

Code for connecting
    Public Sub Run(ByVal configFile As String)

    End Sub

   Public Sub fromApp(ByVal message As QuickFix.Message, ByVal sessionID
As QuickFix.SessionID) Implements QuickFix.Application.fromApp
        'Utils.Log("from app - rates")
        'Utils.Log(message.ToString)
        crack(message, sessionID)
    End Sub

    Public Sub send(ByVal message As QuickFix.Message)
        Try
            QuickFix.Session.sendToTarget(message, m_sessionID)
        Catch ex As Exception
            Utils.Log(ex.Message)
        End Try
    End Sub

I will appreciate your help.

Thanks

PS

Hi,

This is may be a horrible way of resetting the session but it is serving
my purpose. 

I have set of currency pairs AUD/USD, EUR/USD, AUD/SGD etc, I pass one
e.g. AUD/USD currency pair into my sendToTarget session and receive a
message which I manipulate in to xml file.

All my currency pairs is in datatable

Then it goes back to my fromApp procedure and now I have to send new
currency pair e.g. EUR/USD. To make this successful I have to reset the
session that is by sTest.reset:

crack(Param, Param1)
        Try

            Dim sTest As QuickFix.Session =
QuickFix.Session.lookupSession(Param1)
            If (sTest.isLoggedOn = True) Then
                If (sTest.receivedLogon = True) Then
                    Param.clear()
                    sTest.reset()
                    Exit Sub
                End If
            End If

The reset takes me back to the OnLogon function and start with new set
of currency e.g. EUR/USD.

Every time I see the message in console..."existing session was
forcefully closed by host".

At the moment this is working fine but if you have better way of doing,
please do share with me.

Another issue, I want to log errors in error log file. Is there a way to
do in QuickFix.

Thanks for your help.

PS

Hi Jeff,

You should be aware (and maybe you already are aware) that message 
passing in the FIX world is asynchronous.  There is no concept of 
sending a request and getting one and only one reply to that request the 
way there is in other protocols (CORBA, Java's RMI, Soap, etc.)  Instead 
the counterparty will respond when it has something to say.  A new order 
single message, for example, may eventually trigger five or six replies 
(or more or less) from the exchange.

If you read the FIX protocol specifications for the version of FIX you 
are using (these are available at www.fixprotocol.org) you will find 
sequence diagrams that show the messages that would be exchanged during 
many common scenarios.  Reading and understanding these will give you a 
better feel for what to expect.

HTH,

Dale

Jeff Mathis wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hello, I'm new to quickfix so pardon this question if its in the docs  
> somewhere.
>
> After we call FIX::SESSION:sendToTarget with a Message, what are the  
> sequence of calls to get a message back from the receiver? I'm looking  
> for an acknowledgement that they received my message, and for example  
> in the case of a market buy order whether we got filled and at what  
> price.
>
> I'e looked in the examples and it seem all the communication is one way.
>
> thanks
>
> jeff
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>   

After doing additional reading I find that the performance impact of "-g" is
none, apologies for the false alarm in my previous post. The only scenario
where I can think of a possible performance penalty is during initial load
of the library. Due to its large size it may enforce additional disk seeks,
thus slowing the performance. However I have'nt seen any benchmarks to prove
this hypothesis.

The difference of disk footprint however is considerable. Inherently the
debugging symbols generated for C++ programs are huge. Default quickfix
shared library size is 6.2M, whereas when built without debugging symbols,
its reduced to as low as 1.1M (5-6 times less than the original size).

6.2M is more likely to be a negligible disk footprint for most people, hence
there is no harm in ignoring this for now.

thanks,
-- Sibte

On Wed, Apr 30, 2008 at 2:21 PM, <or...@qu...> wrote:

> How do including debug symbols make things any slower?  I've never heard
> of this.  Running the performance tests with and without is yielding no
> different results.
>
> > Is there any specific reason why we are setting the default compiler
> flags
> > for *nix systems to "-g"?
> > Would'nt it make more sense to exclude "-g" so that the compiled library
> is
> > smaller and faster?
> > thanks,
>
>
>

The callbacks get called whenever you receive a message from the
counterparty.  What messages they send you is something you have to work
out with them.

> I guess specifically I'm wanting to find out the timing of calls to  
> fromApp and onMessage. Is this something to work out with the receiver?
> On Apr 30, 2008, at 1:03 PM, Jeff Mathis wrote:
> > Hello, I'm new to quickfix so pardon this question if its in the docs
> > somewhere.
> >
> > After we call FIX::SESSION:sendToTarget with a Message, what are the
> > sequence of calls to get a message back from the receiver? I'm looking
> > for an acknowledgement that they received my message, and for example
> > in the case of a market buy order whether we got filled and at what
> > price.
> >
> > I'e looked in the examples and it seem all the communication is one  
> > way.
> >
> > thanks
> >
> > jeff
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> > Don't miss this year's exciting event. There's still time to save  
> > $100.
> > Use priority code J8TL2D2.
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> > https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> >
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

I guess specifically I'm wanting to find out the timing of calls to  
fromApp and onMessage. Is this something to work out with the receiver?

On Apr 30, 2008, at 1:03 PM, Jeff Mathis wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hello, I'm new to quickfix so pardon this question if its in the docs
> somewhere.
>
> After we call FIX::SESSION:sendToTarget with a Message, what are the
> sequence of calls to get a message back from the receiver? I'm looking
> for an acknowledgement that they received my message, and for example
> in the case of a market buy order whether we got filled and at what
> price.
>
> I'e looked in the examples and it seem all the communication is one  
> way.
>
> thanks
>
> jeff
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

Hello, I'm new to quickfix so pardon this question if its in the docs  
somewhere.

After we call FIX::SESSION:sendToTarget with a Message, what are the  
sequence of calls to get a message back from the receiver? I'm looking  
for an acknowledgement that they received my message, and for example  
in the case of a market buy order whether we got filled and at what  
price.

I'e looked in the examples and it seem all the communication is one way.

thanks

jeff

How do including debug symbols make things any slower?  I've never heard
of this.  Running the performance tests with and without is yielding no
different results.

> Is there any specific reason why we are setting the default compiler flags
> for *nix systems to "-g"?
> Would'nt it make more sense to exclude "-g" so that the compiled library is
> smaller and faster?
> thanks,

Is there any specific reason why we are setting the default compiler flags
for *nix systems to "-g"?

Would'nt it make more sense to exclude "-g" so that the compiled library is
smaller and faster?

thanks,
-- Sibte

>As I understand it, some exchanges will use FIX as an interface to their
>older, internal order routing system, and it is the older systems that have
>these requirements.

Perfect! That's exactly my case.
Thanks a lot.

Kenny Stone wrote:
> 
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> 
> I wouldn't say that this is common behavior, but each implementation of
> FIX
> by an exchange has its own specification, often with quirks, and ClOrdId
> is
> one of the fields that most often has requirements attached to it.
> 
> As I understand it, some exchanges will use FIX as an interface to their
> older, internal order routing system, and it is the older systems that
> have
> these requirements.
> 
> 
> From: Motl <hi...@ma...>
>> To: qui...@li...
>> Sent: Tuesday, April 29, 2008 2:25:29 AM
>> Subject: [Quickfix-developers] ClOrdId tag
>>
>> QuickFIX Documentation:
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>> Hi,
>>
>> I have a question regarding ClOrdId tag (11). The FIX specification only
>> requires this field to be unique within a day (or across days for
>> multi-day
>> orders), but says nothing about "incremental" format of this field. But
>> I'm
>> working with a FIX implementation that only accepts orders with ClOrdId
>> tag
>> like "UNIQORDID1001",
>> "UNIQORDID1002".
>>
>> Is this a common behavior?
>>
>> Thanks.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/ClOrdId-tag-tp16953721p16953721.html
>> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>> Don't miss this year's exciting event. There's still time to save $100.
>> Use priority code J8TL2D2.
>>
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

-- 
View this message in context: http://www.nabble.com/ClOrdId-tag-tp16953721p16969165.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

John,

Within your toAdmin() function do something like this and they will be
appended to all messages.  The CME requires this.

public void toAdmin(QuickFix.Message message, QuickFix.SessionID sessionID)
{
            message.getHeader().setField(new SenderSubID("ID"));
            message.getHeader().setField(new TargetSubID("ID"));
}

-- 
Shane Trotter
Connamara Systems, LLC

On Tue, Apr 29, 2008 at 2:16 PM, John Haldi <jr...@ya...> wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>
>
>
> I need to connect to an exchange that requires SenderSubID and TargetSubID to be set on *all* messages -- i.e. admin messages as well as app messages.
>
> I've done this in the past on actual orders which I create in my app by setting the fields individually by pullling the header and setting the fields, but I've never tried to stitch them into my app such that they are inserted into the logon messages, sequencing messages, etc.
>
> What's the "path of least resistance" to accomplish this?  I was hoping that these might be fields I could set in the quickfix settings file, but it seems like this is a no-go.  Could somebody recommend the easiest way to accomplish this?
>
> Thanks,
>
>    John
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

I need to connect to an exchange that requires SenderSubID and TargetSubID to be set on *all* messages -- i.e. admin messages as well as app messages.

I've done this in the past on actual orders which I create in my app by setting the fields individually by pullling the header and setting the fields, but I've never tried to stitch them into my app such that they are inserted into the logon messages, sequencing messages, etc.

What's the "path of least resistance" to accomplish this?  I was hoping that these might be fields I could set in the quickfix settings file, but it seems like this is a no-go.  Could somebody recommend the easiest way to accomplish this?

Thanks,

   John

<html><body>Not sure why it wasn't there.&nbsp; I created a new tag for it.<BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid" webmail="1">-------- Original Message --------<BR>Subject: [Quickfix-developers] where is the 12.4 branch in subversion?<BR>From: "Mark T. Kennedy" &lt;mke...@di...&gt;<BR>Date: Tue, April 29, 2008 10:52 am<BR>To: quickfix developers &lt;<a href="mailto:qui...@li...urceforge">qui...@li...urceforge</a>.net&gt;<BR><BR>QuickFIX Documentation: <A href="http://www.quickfixengine.org/quickfix/doc/html/index.html" target=_blank><a href="http://www.quickfixengine.org/quickfix/doc/html/index.html">http://www.quickfixengine.org/quickfix/doc/html/index.html</a></A><BR>QuickFIX Support: <A href="http://www.quickfixengine.org/services.html" target=_blank><a href="http://www.quickfixengine.org/services.html">http://www.quickfixengine.org/services.html</a></A><BR><BR><BR>under the 'tags' tree, there is no 12.4 subdir. and the trunk doesn't correspond to<BR>files in the 12.4 tar.gz file. is 12.4 in the subversion repository?<BR><BR>/mark<BR><BR>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.<BR><BR><BR>-------------------------------------------------------------------------<BR>This <a href="http://SF.net">SF.net</a> email is sponsored by the 2008 JavaOne(SM) Conference <BR>Don't miss this year's exciting event. There's still time to save $100. <BR>Use priority code J8TL2D2. <BR><A href="http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone" target=_blank><a href="http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone">http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone</a></A><BR>_______________________________________________<BR>Quickfix-developers mailing list<BR><A onclick="Popup.composeWindow('pcompose.php?sendto=Quickfix-developers%40lists.sourceforge.net'); return false;" href="#Compose">Quickfix-developers<B></B>@lists.sourceforge.net</A><BR><A href="https://lists.sourceforge.net/lists/listinfo/quickfix-developers" target=_blank><a href="https://lists.sourceforge.net/lists/listinfo/quickfix-developers">https://lists.sourceforge.net/lists/listinfo/quickfix-developers</a></A><BR></BLOCKQUOTE></body></html>

<html><body><div>Ok.&nbsp; The project planning is done on Basecamp, and the bugs are tracked on the bugtracker, which we actually just redeployed.&nbsp; The bugtracker is available to everyone while basecamp is only available to a few active members at this time.&nbsp; Here is a list of tasks for the next release.&nbsp; Some of these have been completed, some are in progress.</div>
<div>&nbsp;</div>
<div>Support for threaded non blocking sockets</div>
<div>FIX 5.0</div>
<div>Backing up logs (files and database)</div>
<div>Support for dynamic sessions<BR>Implement identifyType for java and C#</div>
<div>Millisecond support for logs (files and database)</div>
<div>Add unit and performance testing to .NET API<BR></div>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid" webmail="1">-------- Original Message --------<BR>Subject: Re: [Quickfix-developers] question about a change on the trunk<BR>toFileLog.h<BR>From: "Mark T. Kennedy" &lt;mke...@di...&gt;<BR>Date: Tue, April 29, 2008 10:11 am<BR>To: quickfix developers &lt;<a href="mailto:qui...@li...urceforge">qui...@li...urceforge</a>.net&gt;<BR><BR>QuickFIX Documentation: <A href="http://www.quickfixengine.org/quickfix/doc/html/index.html" target=_blank><a href="http://www.quickfixengine.org/quickfix/doc/html/index.html">http://www.quickfixengine.org/quickfix/doc/html/index.html</a></A><BR>QuickFIX Support: <A href="http://www.quickfixengine.org/services.html" target=_blank><a href="http://www.quickfixengine.org/services.html">http://www.quickfixengine.org/services.html</a></A><BR><BR><BR>this kind of begs the question - how is this project structured? i can see the sourceforge<BR>subversion list of committers but that doesn't tell me what people are working on, what<BR>is likely to be delivered (e.g. bug fixes, new features), when things will be delivered,<BR>etc.<BR><BR>could someone (oren?) give an overview of:<BR><BR>1) the committers and what they're working on (maintenance, enhancements)?<BR>2) the schedule for both major (new features) and minor (bug fixes) releases?<BR><BR>thanks in advance.<BR><BR>/mark<BR><BR>Mike Gatny wrote:<BR>&gt; QuickFIX Documentation: <A href="http://www.quickfixengine.org/quickfix/doc/html/index.html" target=_blank><a href="http://www.quickfixengine.org/quickfix/doc/html/index.html">http://www.quickfixengine.org/quickfix/doc/html/index.html</a></A><BR>&gt; QuickFIX Support: <A href="http://www.quickfixengine.org/services.html" target=_blank><a href="http://www.quickfixengine.org/services.html">http://www.quickfixengine.org/services.html</a></A><BR>&gt; <BR>&gt; I didn't actually add the timestamp -- I did however add milliseconds to it.<BR>&gt; <BR><BR>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.<BR><BR><BR>-------------------------------------------------------------------------<BR>This <a href="http://SF.net">SF.net</a> email is sponsored by the 2008 JavaOne(SM) Conference <BR>Don't miss this year's exciting event. There's still time to save $100. <BR>Use priority code J8TL2D2. <BR><A href="http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone" target=_blank><a href="http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone">http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone</a></A><BR>_______________________________________________<BR>Quickfix-developers mailing list<BR><A onclick="Popup.composeWindow('pcompose.php?sendto=Quickfix-developers%40lists.sourceforge.net'); return false;" href="#Compose">Quickfix-developers<B></B>@lists.sourceforge.net</A><BR><A href="https://lists.sourceforge.net/lists/listinfo/quickfix-developers" target=_blank><a href="https://lists.sourceforge.net/lists/listinfo/quickfix-developers">https://lists.sourceforge.net/lists/listinfo/quickfix-developers</a></A><BR></BLOCKQUOTE></body></html>

under the 'tags' tree, there is no 12.4 subdir.  and the trunk doesn't correspond to
files in the 12.4 tar.gz file.  is 12.4 in the subversion repository?

/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.

this kind of begs the question - how is this project structured?  i can see the sourceforge
subversion list of committers but that doesn't tell me what people are working on, what
is likely to be delivered (e.g. bug fixes, new features), when things will be delivered,
etc.

could someone (oren?) give an overview of:

1) the committers and what they're working on (maintenance, enhancements)?
2) the schedule for both major (new features) and minor (bug fixes) releases?

thanks in advance.

/mark

Mike Gatny wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> I didn't actually add the timestamp -- I did however add milliseconds to it.
> 

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.

I didn't actually add the timestamp -- I did however add milliseconds to it.

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

<html><body>They are still in the database.&nbsp; We'll try to&nbsp;import whatever is still relevant.&nbsp; If there is an issue you added that is still outstanding it would be helpful if you can add it to the new one.<BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid" webmail="1">-------- Original Message --------<BR>Subject: Re: [Quickfix-developers] New bugtracker for QuickFIX deployed<BR>From: "Igor Seleznev" &lt;se...@tb...&gt;<BR>Date: Tue, April 29, 2008 8:47 am<BR>To: &lt;or...@qu...&gt;,<BR>&lt;<a href="mailto:Qui...@li...urceforge">Qui...@li...urceforge</a>.net&gt;<BR><BR>
<STYLE></STYLE>

<DIV><FONT size=2>Hi,</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Will the issues from the old bugtracker be migrated to the new system, or they are gone?</FONT></DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> <A <a href="mailto:title=or...@qu...">title=or...@qu...</a> onclick="Popup.composeWindow('pcompose.php?sendto=oren%40quickfixengine.org');; return false;" href="mailto:or...@qu..." target=_blank><a href="mailto:or...@qu...">or...@qu...</a></A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, April 25, 2008 8:42 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [Quickfix-developers] New bugtracker for QuickFIX deployed</DIV>
<DIV><FONT size=2></FONT><BR></DIV><BR>
<div>
<div></div>
<DIV>So as many of you have noticed the old bugtrcker was causing a lot of problems and was becoming overrun by spam bots.&nbsp; We've axed the old bugtracker and deployed a new one which uses the Arctic bugtracker.&nbsp; It is available at the same location, <A href="http://www.quickfixengine.org/bugtracker" target=_blank><A href="http://www.quickfixengine.org/bugtracker" target=_blank><a href="http://www.quickfixengine.org/bugtracker">http://www.quickfixengine.org/bugtracker</a></A></A></DIV>
<P><FONT size=2></FONT></div></BLOCKQUOTE></BLOCKQUOTE></body></html>

I don't think it's common behavior, you are correct that the actual
specification is that it has to be unique within a day.  It sounds like the
counterparty's FIX system is bolted on top of an existing platform with
those constraints.

On Tue, Apr 29, 2008 at 2:25 AM, Motl <hi...@ma...> wrote:

> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Hi,
>
> I have a question regarding ClOrdId tag (11). The FIX specification only
> requires this field to be unique within a day (or across days for
> multi-day
> orders), but says nothing about "incremental" format of this field. But
> I'm
> working with a FIX implementation that only accepts orders with ClOrdId
> tag
> like "UNIQORDID1001",
> "UNIQORDID1002".
>
> Is this a common behavior?
>
> Thanks.
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/ClOrdId-tag-tp16953721p16953721.html
> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

-- 
Shane Trotter
Connamara Systems, LLC

Hi,

Will the issues from the old bugtracker be migrated to the new system, or they are gone?

  ----- Original Message ----- 
  From: or...@qu... 
  Sent: Friday, April 25, 2008 8:42 PM
  Subject: [Quickfix-developers] New bugtracker for QuickFIX deployed

  So as many of you have noticed the old bugtrcker was causing a lot of problems and was becoming overrun by spam bots.  We've axed the old bugtracker and deployed a new one which uses the Arctic bugtracker.  It is available at the same location, http://www.quickfixengine.org/bugtracker

I wouldn't say that this is common behavior, but each implementation of FIX
by an exchange has its own specification, often with quirks, and ClOrdId is
one of the fields that most often has requirements attached to it.

As I understand it, some exchanges will use FIX as an interface to their
older, internal order routing system, and it is the older systems that have
these requirements.

From: Motl <hi...@ma...>
> To: qui...@li...
> Sent: Tuesday, April 29, 2008 2:25:29 AM
> Subject: [Quickfix-developers] ClOrdId tag
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Hi,
>
> I have a question regarding ClOrdId tag (11). The FIX specification only
> requires this field to be unique within a day (or across days for
> multi-day
> orders), but says nothing about "incremental" format of this field. But
> I'm
> working with a FIX implementation that only accepts orders with ClOrdId
> tag
> like "UNIQORDID1001",
> "UNIQORDID1002".
>
> Is this a common behavior?
>
> Thanks.
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/ClOrdId-tag-tp16953721p16953721.html
> Sent from the QuickFIX - Dev mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2002	Jan	Feb (5)	Mar (16)	Apr (15)	May (17)	Jun (33)	Jul (35)	Aug (34)	Sep (19)	Oct (40)	Nov (51)	Dec (43)
2003	Jan (45)	Feb (79)	Mar (124)	Apr (121)	May (132)	Jun (77)	Jul (110)	Aug (57)	Sep (48)	Oct (83)	Nov (60)	Dec (40)
2004	Jan (67)	Feb (72)	Mar (74)	Apr (87)	May (70)	Jun (96)	Jul (75)	Aug (147)	Sep (128)	Oct (83)	Nov (67)	Dec (42)
2005	Jan (110)	Feb (84)	Mar (68)	Apr (55)	May (51)	Jun (192)	Jul (111)	Aug (100)	Sep (79)	Oct (127)	Nov (73)	Dec (112)
2006	Jan (95)	Feb (120)	Mar (138)	Apr (127)	May (124)	Jun (97)	Jul (103)	Aug (88)	Sep (138)	Oct (91)	Nov (112)	Dec (57)
2007	Jan (55)	Feb (35)	Mar (56)	Apr (16)	May (20)	Jun (77)	Jul (43)	Aug (47)	Sep (29)	Oct (54)	Nov (39)	Dec (40)
2008	Jan (69)	Feb (79)	Mar (122)	Apr (106)	May (114)	Jun (76)	Jul (83)	Aug (71)	Sep (53)	Oct (75)	Nov (54)	Dec (43)
2009	Jan (32)	Feb (31)	Mar (64)	Apr (48)	May (38)	Jun (43)	Jul (35)	Aug (15)	Sep (52)	Oct (62)	Nov (62)	Dec (21)
2010	Jan (44)	Feb (10)	Mar (47)	Apr (22)	May (5)	Jun (54)	Jul (19)	Aug (54)	Sep (16)	Oct (15)	Nov (7)	Dec (8)
2011	Jan (18)	Feb (9)	Mar (5)	Apr (5)	May (41)	Jun (40)	Jul (29)	Aug (17)	Sep (12)	Oct (23)	Nov (22)	Dec (11)
2012	Jan (8)	Feb (24)	Mar (5)	Apr (5)	May (6)	Jun (5)	Jul (5)	Aug (5)	Sep (2)	Oct (9)	Nov (2)	Dec (18)
2013	Jan (25)	Feb (16)	Mar (8)	Apr (2)	May (16)	Jun (17)	Jul (2)	Aug (13)	Sep (3)	Oct (4)	Nov (1)	Dec
2014	Jan (2)	Feb	Mar (22)	Apr (9)	May (3)	Jun (1)	Jul (5)	Aug (11)	Sep (18)	Oct (4)	Nov (4)	Dec (3)
2015	Jan (2)	Feb	Mar	Apr (3)	May (4)	Jun (37)	Jul	Aug (4)	Sep (6)	Oct (1)	Nov (4)	Dec (2)
2016	Jan (9)	Feb (3)	Mar (7)	Apr (1)	May (8)	Jun	Jul	Aug	Sep (7)	Oct (3)	Nov (16)	Dec
2017	Jan (1)	Feb (15)	Mar (2)	Apr (12)	May (4)	Jun (7)	Jul (5)	Aug	Sep	Oct	Nov (23)	Dec (8)
2018	Jan (2)	Feb (4)	Mar (2)	Apr (8)	May (3)	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec
2019	Jan	Feb (1)	Mar	Apr	May	Jun	Jul (1)	Aug (1)	Sep	Oct (5)	Nov (3)	Dec
2020	Jan	Feb (4)	Mar (3)	Apr	May	Jun	Jul (12)	Aug (5)	Sep (3)	Oct (1)	Nov	Dec (1)
2021	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug (2)	Sep	Oct	Nov	Dec
2022	Jan	Feb (1)	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2025	Jan	Feb	Mar	Apr (1)	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

quickfix-developers Mailing List for QuickFIX (Page 85)

quickfix-developers — QuickFIX developers forum