quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] Issues with QuickFix .NET 2

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

Have you distributed it with the C++ runtime dlls?

--oren

On May 3, 2007, at 11:04 AM, Gary Grant wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi all,
>
> I've created an application using QuickFix for .NET 2.0 and created  
> an installer for the appliation. When I install it on a machine  
> with Visual Studio, the application works. If I install it on a  
> machine without, it seems that the Dll do not load up. Is anyone  
> aware of this issue and how to get around it?
>
> Cheers
>
> Gary
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/ 
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] Issues with QuickFix .NET 2

[Gary G. <gar...@gm...>]

Hi all,

I've created an application using QuickFix for .NET 2.0 and created an
installer for the appliation. When I install it on a machine with Visual
Studio, the application works. If I install it on a machine without, it
seems that the Dll do not load up. Is anyone aware of this issue and how to
get around it?

Cheers

Gary

Re: [Quickfix-developers] quickfix & delphi

[LuCiD <nei...@ya...>]

Hi Guys

We are looking at implementing FIX on our trading systems. We are a Delphi
shop. We are using Delphi 6 and 2006. I have looked at your post and being
new to the Delphi.Net arena I have one question... How do I use the
quickfix_net.dll and the quickfix_net_messages.dll in a Delphi.Net
application. I have tried adding a namespace for it with no success even
tried the Import the DLL from the Components Installed .Net Components Menu
and this gives me the message NOT A VALID .Net Assembly. What am I doing
wrong? How do I get Delphi.Net to use these files?

Thanks
Neil

-- 
View this message in context: http://www.nabble.com/quickfix---delphi-tf3472267.html#a10302064
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

[Quickfix-developers] Repeating Groups

[McAndrew, P. <pa...@no...>]

I want to send multi leg orders and I understand I need to use repeating =
groups.  I can't find any example code for sending orders in repeating =
groups in C# and I'm not able to model it after the examples in the =
documentation.  Could someone send me some example code for repeating =
groups to send NewOrderSingle orders?
=20
Thanks, Paige

Re: [Quickfix-developers] Session statring Code

[Caleb E. <cal...@gm...>]

On 4/30/07, SoftwarePattern <mir...@ya...> wrote:

> Does any body give me an example how i can start the session using the quick
> fix and send a message; thanks

There are numerous example programs distributed with the source code.
Download the sources and look at the examples/ directory.

-- 
Caleb Epstein

Re: [Quickfix-developers] session reset

[Mark R. <mr...@pr...>]

Can you tell me when this new release is planned please?

Regards,
Mark

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Oren Miller
Sent: Thursday, March 15, 2007 15:29
To: Caleb Epstein
Cc: qui...@li...
Subject: Re: [Quickfix-developers] session reset

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

FYI, we are adding support for local time in the next release.

--oren

On Mar 15, 2007, at 9:48 AM, Caleb Epstein wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/=20
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> On 3/15/07, Nick Bilak <be...@gm...> wrote:
>> i have a problem of session being reset every day at 17:00EST
>> session is configured as weekly:
>>
>> StartTime=3D00:00:00
>> EndTime=3D00:00:00
>>
>> is my session config wrong or should i get updated version of =20
>> quickfix?
>
> Those times are in GMT.  17:00 EST =3D=3D midnight GMT.
>
> http://quickfixengine.org/quickfix/doc/html/configuration.html
>
> --=20
> Caleb Epstein


------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] Session statring Code

[SoftwarePattern <mir...@ya...>]

Does any body give me an example how i can start the session using the quick
fix and send a message; thanks
-- 
View this message in context: http://www.nabble.com/Session-statring-Code-tf3668186.html#a10249270
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

[Quickfix-developers] ConfigError exception on startup

[Keith M. <km...@us...>]

Hi

I'm developing a GUI which uses QuickFIX and I've come across a problem =
when the host defined by SocketConnectHost is unavailable. What appears =
to happen is QuickFIX then tries SocketConnectHost0 (which is undefined) =
and throws a ConfigError exception "SocketConnectHost0 not defined". =
Trouble is, because the SocketInitiator is running in a different  =
thread, the application never gets to catch that exception. Has anyone =
found a way round this, or as is most likely, have I've missed something =
simple?

Using MS Visual Studio 2005 on WinXP and QuickFIX Version 1.12.4

Thanks and regards

Keith

Re: [Quickfix-developers] multi SocketAcceptPort definition for Acceptor

[Djalma R. d. S. F. <drs...@gm...>]

Yes, it is possible. If  the QF version you are using is above 1.12.

In quickfix/NEWS you will find the following:

1.12.0
------
SocketAcceptor and ThreadedSocketAcceptor can listen for connections on
multiple ports.  SocketAcceptPort no longer needs to be in the DEFAULT
section and can be assigned to sessions.  Sessions can share accepting
ports like before.

Isn't it working for you?

Regards,
Djalma

On 4/24/07, Petr Postulka <pet...@em...> wrote:
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi all,
>
> I want to ask if it is possible to specify different socket ports for
> different sessions on Acceptor.
> Something like this:
>
> # default settings for sessions
>   [DEFAULT]
>   ConnectionType=acceptor
>   SocketAcceptPort=5005 <-this one I want to override
>   HeartBtInt=30
>   FileLogPath=...
>   FileStorePath=...
>
>   [SESSION]
>   TargetCompID=Session1
>   BeginString=FIX.4.1
>   SenderCompID=Sender
>   StartTime=06:30:00
>   EndTime=05:30:00
>   HeartBtInt=30
>   SocketAcceptPort=1 <- here Im overriding socket port for this session
>   DataDictionary=...
>   CheckLatency=N
>
>   [SESSION]
>   TargetCompID=Session2
>   BeginString=FIX.4.1
>   SenderCompID=Sender
>   StartTime=06:30:00
>   EndTime=05:30:00
>   HeartBtInt=30
>   SocketAcceptPort=2  <- here Im overriding socket port for this session
>   DataDictionary=...
>   CheckLatency=N
>
> Or if it is not possible, is there some other way, how to solve it?
>
> Thanks for your help.
>
> Petr Postulka
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

[Quickfix-developers] multi SocketAcceptPort definition for Acceptor

[<pet...@em...>]

Hi all,

I want to ask if it is possible to specify different socket ports for different sessions on Acceptor.
Something like this:

# default settings for sessions
  [DEFAULT]
  ConnectionType=acceptor
  SocketAcceptPort=5005 <-this one I want to override
  HeartBtInt=30
  FileLogPath=...
  FileStorePath=...

  [SESSION]
  TargetCompID=Session1 
  BeginString=FIX.4.1
  SenderCompID=Sender
  StartTime=06:30:00
  EndTime=05:30:00
  HeartBtInt=30
  SocketAcceptPort=1 <- here Im overriding socket port for this session
  DataDictionary=...
  CheckLatency=N

  [SESSION]
  TargetCompID=Session2 
  BeginString=FIX.4.1
  SenderCompID=Sender
  StartTime=06:30:00
  EndTime=05:30:00
  HeartBtInt=30
  SocketAcceptPort=2  <- here Im overriding socket port for this session
  DataDictionary=...
  CheckLatency=N

Or if it is not possible, is there some other way, how to solve it?

Thanks for your help.

Petr Postulka

Re: [Quickfix-developers] Howto specify explicitly order of custom fields?

[JohnG <jo...@pu...>]

I am having the same difficulty with the order of custom header fields. I a=
m
unable to add EMX field 9426 to the header in the right order. Did you find
a solution to this problem ?

Thanks, John


Oren Miller wrote:
>=20
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
>=20
> Well, if you dig down into the C++ layer, in the FieldMap class, you =20
> will notice that a FieldMap constructor takes a message_order =20
> object.  Now, if you look in MessageSorters.h, you will find the =20
> message_order object which has 4 modes.
>=20
> header: Makes sure that the BeginString, BodyLength, and MsgType are =20
> the first three fields.  Everything else in ascending numerical order.
>=20
> trailer: Makes sure the CheckSum field is last.  Everything else in =20
> ascending numerical order.
>=20
> normal: Sorted in ascending numerical order, used for message body's
>=20
> group: Sorted in the order based on provided list.
>=20
> Why is it like this?  Well sorting things in ascending order is just =20
> the simplest fastest way to sort fields and complies with the spec.  =20
> The group order was introduced because the spec explicitly states =20
> that repeating groups must be in a specific order.
>=20
> Basically to accomplish what you need would require some new =20
> functionality.  I think it would require the implementation of a data =20
> dictionary sorting mode.
>=20
> --oren
>=20
> On Jul 15, 2005, at 11:27 AM, Joerg Thoennes wrote:
>=20
>> Hi Oren,
>>
>>
>>> Which fields need to be ordered?  The custom tags in the header =20
>>> and  the trailer?  The entire message?
>>>
>>
>> To be more precise: EMX adds extra custom fields to both the header =20
>> and trailer, and of course to the body.
>>
>> We generated the new QF classes using the XML scripts, but the =20
>> order seems to be different from what EMX expects.
>>
>> So our questions is:
>>
>> How can we control the order of tags in
>>
>> (a) header
>> (b) body
>> (c) trailer
>>
>> My guess is that the DD order controls at least the body order, but =20
>> I am not sure about header and trailer. After some digging of the =20
>> source code some advise from you would be very helpful.
>>
>> Thanks, J=C3=B6rg
>>
>> --=20
>> Joerg Thoennes
>>                                http://macd.com
>> Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
>> Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen
>>
>>
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dclick
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>=20
>=20

--=20
View this message in context: http://www.nabble.com/Howto-specify-explicitl=
y-order-of-custom-fields--tf148484.html#a10159273
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] Initiator issues

[Sean K. <sea...@pi...>]

>=20
> On 4/19/07, Sean Kirkpatrick <sea...@pi...>
> wrote:
> > I'm trying to run a QuickFIX (1.12.4) app with multiple initiator
> sessions.
> > Problem is, when one of the hosts that I am attempting to connect to
is
> > unavailable, the app hangs and has to be killed.  In the event_log,
> there is
> > a single "Connecting to" entry with the invalid IP.  Has anyone had
> similar
> > issues?
>=20
> Are you using the ThreadedSocketInitiator?
>=20

Yes, I am.

-Sean


Disclaimer: Any references to Pipeline performance contained herein are =
based on historic performance levels which Pipeline expects to maintain =
or exceed but nevertheless does not guarantee. Congested networks, price =
volatility, or other extraordinary events may impede future trading =
activities and degrade performance statistics.

Re: [Quickfix-developers] Initiator issues

[Caleb E. <cal...@gm...>]

On 4/19/07, Sean Kirkpatrick <sea...@pi...> wrote:
> I'm trying to run a QuickFIX (1.12.4) app with multiple initiator sessions.
> Problem is, when one of the hosts that I am attempting to connect to is
> unavailable, the app hangs and has to be killed.  In the event_log, there is
> a single "Connecting to" entry with the invalid IP.  Has anyone had similar
> issues?

Are you using the ThreadedSocketInitiator?

-- 
Caleb Epstein

[Quickfix-developers] New Algo Std @ FIX, hot XML implementation

[Rick L. <ri...@cl...>]

Just wanted to give Quickfix developers a heads up on the rapidly emerging
new algo standard at FIX, and ask for some specific feedback on two open
issues. See http://www.fixprotocol.org/algostandard for the standard and the
sample files.

The FIX Algo committee would very much welcome QuickFix developer input into
refining the standard into something that smoothly integrates with the rest
of what you are doing with QuickFix in open source. The comment period ahead
of pilot testing runs through April. After that pilot tests begin, the
process starts to become significantly more rigid.

We have a few open issues that are being worked on the work group. See the
issues documents at the above address for the full listing. Here are two
however that may be of specific interest to QuickFix developers I'll cover
right here.

Number one, as part of this algo draft standard, but also for other
initiatives, FIX is in process of exposing all its XML (.xsd files) in a
public directory, accessible on a file by file uncompressed basis, with no
delay, no registrations -- wide open for all who come to get them.

Each file will contain a comment similar to the following (in draft form):

***
Copyright 2007 FIX Protocol Ltd. See usage license at:
http://fixprotocol.org/copyright.shtml

WARNING: Locally Cache These files! Numerous problems can impede access to
these files on a timely basis, many of which are not controllable by FIX.
Problems include, but are not limited to, network outages in any hop between
FIX and your destination, file caching schemes deployed by various ISP along
the route, name to IP number resolution and other DNS issues, router table
error or corruption at any hop, FIX web server technical difficulty, network
congestion on links or within routers, web server and back end database
server loads, loads on servers located adjacent to FIX web servers, power
failures, viruses and corruption, hardware failures, etc. FIX cannot be held
responsible for any delays in your receipt of these files.

Furthermore there is no guarantee that the files will not be changed in the
future. Errors or inconsistencies may be introduced into these files at any
time, even during the performance of minor maintenance. Changes to these
files may be inconsistent with your implementation. There is no guarantee
that version numbers on files will always increment with a minor change. FIX
is not responsible for any usage of these files whatsoever.

Also note that these files will not be made available indefinitely. It's
currently planned that only frequently accessed files will remain available,
generally the most current three versions or less. There is no guarantee
that a historical achieve will be maintained or if one exists that it will
cover all files ever issued by FIX. Do not rely on FIX to be a permanent
backup to files essential to your operation.
***

Obviously, the above is for legal purposed to protect FIX from damage claims
in an outage. FIX intends however to operate highly reliable web servers
with great connections, ample bandwidth, and be able to serve up the files
whenever needed. Further, it's not intended that there will be a new Algo
standard coming out of FIX any more frequently than every two or more years.
Still, the algo area is volatile and rapidly evolving, so I think you can
see where this may be headed.

Question #1 what is your reaction to the above? Does this make life better
or more miserable for a FIX engine developer? Any additional things we need
to consider as more frequent updates to FIX become more specialized and
frequent? (There are a number of extensions and service packs in the
development cue at FIX.)

Question #2 any thoughts on where we should be headed with validation?
Here's the current "to be looked at" list:
Schematron
CLIX
http://nrl.sourceforge.net/
http://www.omg.org/technology/documents/modeling_spec_catalog.htm#OCL
http://www.ruleml.org/
It's likely we will not do anything other than the simplest validation -- a
very basic and limited sub segment common across all of the above "rule
engines" -- in Version 1.0 of the new algo standard. However after that
ships we will be looking to tighten up this considerably as it's a huge area
of miscommunication between Broker Dealer providers of algos and Order
Management System / Buy Side users. Any ideas how best to do additional
validation beyond which the base level of XML accomplishes?

Comments and observations are very much appreciated. Anything sent to
alg...@fi... will hit every member of the technical work group
at FIX and be carefully considered.

Thanks very much.

The Fix Algorithmic Trading Working Group

[Quickfix-developers] Why BerkeleyDB is not used in QuickFIX?

[Djalma R. d. S. F. <drs...@gm...>]

Ly8vIEBjbGFzcyAgQkRCTXNnU3RvcmUNCi8vLyBAYnJpZWYgIFF1aWNrRklYIE1lc3NhZ2VTdG9y
ZSB1c2luZyBCZXJrZWxleSBEQiBmb3IgcGVyc2lzdGVuY2UNCi8vLyBAYXV0aG9yIENhbGViIEVw
c3RlaW4NCi8vLw0KLy8vICRJZCQNCiNpZm5kZWYgSEFWRV9CRVJLRUxFWURCDQojZXJyb3IgQkRC
U3RvcmUuaCBpbmNsdWRlZCwgYnV0IEhBVkVfQkVSS0VMRVlEQiBub3QgZGVmaW5lZA0KI2VuZGlm
DQoNCiNpZmRlZiBIQVZFX0JFUktFTEVZREINCiNpZm5kZWYgX19CREJNc2dTdG9yZV9oX2luY2wN
CiNkZWZpbmUgX19CREJNc2dTdG9yZV9oX2luY2wNCg0KI2lmZGVmIF9NU0NfVkVSDQojcHJhZ21h
IHdhcm5pbmcoIGRpc2FibGUgOiA0NTAzIDQzNTUgNDc4NiA0MjkwICkNCiNpZiBkZWZpbmVkKF9E
RUJVRykNCiNwcmFnbWEgY29tbWVudCggbGliLCAibGliZGI0NWQubGliIiApDQojZWxzZQ0KI3By
YWdtYSBjb21tZW50KCBsaWIsICJsaWJkYjQ1LmxpYiIgKQ0KI2VuZGlmDQojZW5kaWYNCg0KI2lu
Y2x1ZGUgPGV4Y2VwdGlvbj4NCiNpbmNsdWRlIDxzeXMvdHlwZXMuaD4NCiNpbmNsdWRlIDxzeXMv
c3RhdC5oPg0KLy8jaW5jbHVkZSA8dW5pc3RkLmg+DQoNCiNpbmNsdWRlIDxkYl9jeHguaD4NCg0K
DQojaW5jbHVkZSAiTWVzc2FnZVN0b3JlLmgiDQojaW5jbHVkZSAiU2Vzc2lvblNldHRpbmdzLmgi
DQoNCi8vIEZvcndhcmQgZGVjbGFyYXRpb25zIG9mIEJlcmtlbGV5IERCIGNsYXNzZXMNCi8vY2xh
c3MgRGI7DQovL2NsYXNzIERiRW52Ow0KDQpuYW1lc3BhY2UgRklYIHsNCg0KLy8vIEEgQmVya2Vs
ZXkgREItYmFja2VkIFF1aWNrRklYIE1lc3NhZ2VTdG9yZS4NCi8vLyBAbm90ZQ0KLy8vIENvbnRh
aW5zIHR3byBEQl9SRUNOTyBkYXRhYmFzZXMgKHdoaWNoIGxpdmUgaW4gYSBzaW5nbGUgZmlsZSku
DQovLy8gVGhlIG1zZ2RiXyBkYXRhYmFzZSBwZXJzaXN0cyBvdXRib3VuZCBtZXNzYWdlcyBhbmQg
dGhlIHNlcWRiXw0KLy8vIGRhdGFiYXNlIHBlcnNpc3RzIHRoZSBzZXNzaW9uIGNyZWF0aW9uIHRp
bWUgYW5kIHRoZSBuZXh0IGV4cGVjdGVkDQovLy8gc2VuZGVyIHNlcXVlbmNlIG51bWJlci4NCmNs
YXNzIEJEQk1zZ1N0b3JlIDogcHVibGljIE1lc3NhZ2VTdG9yZSANCnsNCnB1YmxpYzoNCiAgICAv
Ly8gQ3JlYXRlIGEgQkRCTXNnU3RvcmUgdXNpbmcgdGhlIHN1cHBsaWVkIEJlcmtlbGV5IERCDQog
ICAgLy8vIGVudmlyb25tZW50IGZvciB0aGUgc3BlY2lmaWVkIHNlc3Npb24gYW5kIHJlYWRpbmcg
c2V0dGluZ3MNCiAgICAvLy8gZnJvbSB0aGUgc3VwcGxpZWQgRGljdGlvbmFyeQ0KICAgIEJEQk1z
Z1N0b3JlIChEYkVudiogZW52LA0KICAgICAgICAgICAgICAgICBjb25zdCBTZXNzaW9uSUQmIHNl
c3MsDQogICAgICAgICAgICAgICAgIGNvbnN0IERpY3Rpb25hcnkmIHNldHRpbmdzKTsNCg0KICAg
IC8vLyBDbG9zZXMgdGhlIGRhdGFiYXNlcy4NCiAgICB2aXJ0dWFsIH5CREJNc2dTdG9yZSAoKTsN
Cg0KICAgIC8vLyBXcml0ZSBhIG1lc3NhZ2UgdG8gdGhlIHN0b3JlDQogICAgYm9vbCBzZXQgKGlu
dCwgY29uc3Qgc3RkOjpzdHJpbmcmKSB0aHJvdyAoSU9FeGNlcHRpb24pOw0KDQogICAgLy8vIEdl
dCBhIG1lc3NhZ2UgZnJvbSB0aGUgc3RvcmUNCiAgICBib29sIGdldCAoaW50LCBzdGQ6OnN0cmlu
ZyYpIGNvbnN0IHRocm93IChJT0V4Y2VwdGlvbik7DQoNCiAgICAvLy8gR2V0IGEgcmFuZ2Ugb2Yg
bWVzc2FnZXMgZnJvbSB0aGUgc3RvcmUNCiAgICB2b2lkIGdldCAoaW50LCBpbnQsIHN0ZDo6dmVj
dG9yPHN0ZDo6c3RyaW5nPiYpIGNvbnN0DQogICAgICAgIHRocm93IChJT0V4Y2VwdGlvbik7DQoN
CiAgICAvLy8gR2V0IHRoZSBuZXh0IHNlcXVlbmNlIG51bWJlciBleHBlY3RlZCBmcm9tIHRoZSBj
b3VudGVycGFydA0KICAgIGludCBnZXROZXh0U2VuZGVyTXNnU2VxTnVtICgpIGNvbnN0IHRocm93
IChJT0V4Y2VwdGlvbik7DQoNCiAgICAvLy8gR2V0IHRoZSBuZXh0IHNlcXVlbmNlIG51bWJlciB3
ZSB3aWxsIHNlbmQNCiAgICBpbnQgZ2V0TmV4dFRhcmdldE1zZ1NlcU51bSAoKSBjb25zdCB0aHJv
dyAoSU9FeGNlcHRpb24pOw0KDQogICAgLy8vIFNldCB0aGUgbmV4dCBzZXF1ZW5jZSBudW1iZXIg
d2Ugd2lsbCBzZW5kDQogICAgLy8vDQogICAgLy8vIEBub3RlIFRoaXMgbWV0aG9kIHdpbGwgdGhy
b3cgYW4gSU9FeGNlcHRpb24uICBCZWNhdXNlIHRoZQ0KICAgIC8vLyB1bmRlcmx5aW5nIHN0b3Jh
Z2UgZm9ybWF0IGVuZm9yY2VzIHJlY29yZCBudW1iZXJzLCB3ZSBjYW5ub3QNCiAgICAvLy8gY29u
dHJvbCB0aGUgbmV4dCBvbmUgdGhhdCB3aWxsIGJlIGdlbmVyYXRlZCB3aXRob3V0IHJlbW92aW5n
DQogICAgLy8vIG1lc3NhZ2VzIGZyb20gdGhlIHN0b3JlIChpbiB0aGUgY2FzZSBvZiB0aGUgc2Vx
dWVuY2UgbnVtYmVyDQogICAgLy8vIGJlaW5nIGRlY3JlYXNlZCkgb3IgY3JlYXRpbmcgbmV3ICJl
bXB0eSIgb25lcyAoaW5jcmVhc2VkKS4NCiAgICB2b2lkIHNldE5leHRTZW5kZXJNc2dTZXFOdW0g
KGludCB2YWx1ZSkgdGhyb3cgKElPRXhjZXB0aW9uKTsNCg0KICAgIC8vLyBTZXQgdGhlIG5leHQg
c2VxdWVuY2UgbnVtYmVyIGV4cGVjdGVkIGZyb20gdGhlIGNvdW50ZXJwYXJ0DQogICAgdm9pZCBz
ZXROZXh0VGFyZ2V0TXNnU2VxTnVtIChpbnQgdmFsdWUpIHRocm93IChJT0V4Y2VwdGlvbik7DQoN
CiAgICAvLy8gQnVtcCB0aGUgbmV4dCBzZXF1ZW5jZSBudW1iZXIgd2Ugd2lsbCBzZW5kDQogICAg
Ly8vDQogICAgLy8vIEBub3RlIEJlY2F1c2UgdGhlIHVuZGVybHlpbmcgZGF0YWJhc2UgZ2VuZXJh
dGVzIHJlY29yZA0KICAgIC8vLyBudW1iZXJzLCB0aGlzIG1ldGhvZCBkb2VzIG5vdGhpbmcuDQog
ICAgdm9pZCBpbmNyTmV4dFNlbmRlck1zZ1NlcU51bSAoKSB0aHJvdyAoSU9FeGNlcHRpb24pOw0K
DQogICAgLy8vIEJ1bXAgdGhlIG5leHQgc2VxdWVuY2UgbnVtYmVyIGV4cGVjdGVkIGZyb20gdGhl
IGNvdW50ZXJwYXJ0DQogICAgdm9pZCBpbmNyTmV4dFRhcmdldE1zZ1NlcU51bSAoKSB0aHJvdyAo
SU9FeGNlcHRpb24pOw0KDQogICAgLy8vIFdoZW4gd2FzIHRoaXMgc2Vzc2lvbiBjcmVhdGVkDQog
ICAgVXRjVGltZVN0YW1wIGdldENyZWF0aW9uVGltZSAoKSBjb25zdCB0aHJvdyAoSU9FeGNlcHRp
b24pOw0KDQogICAgLy8vIFJlc2V0IHRoZSBtZXNzYWdlIHN0b3JlIChlcmFzZXMgYWxsIG1lc3Nh
Z2VzIGFuZCByZXNldHMNCiAgICAvLy8gc2VxdWVuY2UgbnVtYmVycykNCiAgICB2b2lkIHJlc2V0
ICgpIHRocm93IChJT0V4Y2VwdGlvbik7DQoNCgl2b2lkIHJlZnJlc2goKSB0aHJvdyAoIElPRXhj
ZXB0aW9uICk7DQoNCnByaXZhdGU6DQogICAgLy8vIFNhdmUgdGhlIHNlc3Npb24gY3JlYXRpb24g
dGltZQ0KICAgIHZvaWQgc2F2ZV9zZXNzaW9uICgpOw0KDQogICAgLy8vIExvYWQgdGhlIHNlc3Np
b24gY3JlYXRpb24gdGltZQ0KICAgIGJvb2wgcmVhZF9zZXNzaW9uICgpOw0KDQogICAgLy8vIFNl
c3Npb24gY3JlYXRpb24gdGltZQ0KICAgIFV0Y1RpbWVTdGFtcCBjdGltZV87DQoNCiAgICAvLy8g
U2Vzc2lvbiBJRCBpbmZvcm1hdGlvbg0KICAgIFNlc3Npb25JRCBzZXNzaW9uX2lkXzsNCg0KICAg
IC8vLyBUcmFuc2FjdGlvbmFsIGZsYWdzIChEQl9BVVRPX0NPTU1JVCkNCiAgICBpbnQgeGFjdF9m
bGFnc187DQoNCiAgICAvLy8gVGhpcyBkYXRhYmFzZSBjb250YWlucyB0aGUgb3V0Z29pbmcgbWVz
c2FnZXMNCiAgICAvL0RiKiBtc2dkYl87DQoJRGIgbXNnZGJfOw0KDQogICAgLy8vIHRoaXMgZGF0
YWJhc2UgY29udGFpbnMgdGhlIHNlc3Npb24gY3JlYXRpb24gdGltZSBhbmQNCiAgICAvLy8gTGFz
dFRhcmdldFNlcU51bQ0KICAgIC8vRGIqIHNlcWRiXzsNCglEYiBzZXFkYl87DQoNCiAgICAvLy8g
TmV4dCBzZXF1ZW5jZSBudW1iZXIgZXhwZWN0ZWQgZnJvbSB0aGUgdGFyZ2V0DQogICAgaW50IHRh
cmdldF9zZXFudW1fOw0KDQogICAgLy8vIE5leHQgc2VxdWVuY2UgbnVtYmVyIHdlIHdpbGwgc2Vu
ZA0KICAgIGludCBzZW5kZXJfc2VxbnVtXzsNCn07DQoNCi8vLyBBIFF1aWNrRklYIE1lc3NhZ2VT
dG9yZUZhY3RvcnkgdGhhdCBjcmVhdGVzIEJlcmtlbGV5IERCLWJhY2tlZA0KLy8vIE1lc3NhZ2VT
dG9yZXMNCi8vLw0KLy8vIEBub3RlDQovLy8gQ29udGFpbnMgdGhlIEJlcmtlbGV5IERCICJlbnZp
cm9ubWVudCIgaGFuZGxlIHdoaWNoIHdpbGwgYmUgc2hhcmVkDQovLy8gYnkgYWxsIEJEQk1zZ1N0
b3JlIG9iamVjdHMuDQpjbGFzcyBCREJNc2dTdG9yZUZhY3RvcnkgOiBwdWJsaWMgTWVzc2FnZVN0
b3JlRmFjdG9yeSB7DQpwdWJsaWM6DQogICAgQkRCTXNnU3RvcmVGYWN0b3J5IChjb25zdCBTZXNz
aW9uU2V0dGluZ3MmIHNldHRpbmdzKTsNCiAgICB2aXJ0dWFsIH5CREJNc2dTdG9yZUZhY3Rvcnkg
KCk7DQoNCiAgICBNZXNzYWdlU3RvcmUqIGNyZWF0ZSAoY29uc3QgU2Vzc2lvbklEJiBzZXNzKTsN
CiAgICB2b2lkIGRlc3Ryb3kgKE1lc3NhZ2VTdG9yZSogcyk7DQoNCnByaXZhdGU6DQogICAgY29u
c3QgU2Vzc2lvblNldHRpbmdzJiBzZXR0aW5nc187DQoNCiAgICAvLy8gVGhlIEJlcmtlbGV5IERC
IGVudmlyb25tZW50IHRoYXQgd2lsbCBiZSBzaGFyZWQgYnkgYWxsDQogICAgLy8vIHNlc3Npb25z
IHVzaW5nIHRoZSBCZXJrZWxleSBEQiBNZXNzYWdlU3RvcmUNCiAgICAvL0RiRW52KiBlbnZfOw0K
CS8vRGJFbnYgZW52T2JqXzsNCglEYkVudiBlbnZfOw0KfTsNCg0KfSAvLyBuYW1lc3BhY2UgRklY
DQoNCiNlbmRpZiAvLyBtYWNybyBndWFyZA0KI2VuZGlmIC8vIEhBVkVfQkVSS0VMRVlEQg==

[Quickfix-developers] Initiator issues

[Sean K. <sea...@pi...>]

Hello Everyone,

=20

I'm trying to run a QuickFIX (1.12.4) app with multiple initiator
sessions.  Problem is, when one of the hosts that I am attempting to
connect to is unavailable, the app hangs and has to be killed.  In the
event_log, there is a single "Connecting to" entry with the invalid IP.
Has anyone had similar issues?

=20

Thanks,

-Sean



Disclaimer: Any references to Pipeline performance contained herein are =
based on historic performance levels which Pipeline expects to maintain =
or exceed but nevertheless does not guarantee. Congested networks, price =
volatility, or other extraordinary events may impede future trading =
activities and degrade performance statistics.

[Quickfix-developers] UMR in FIX::Dictionary::getDay

[Igor S. <se...@ma...>]

Hi,

Using Purify tool under Linux I catch the following UMR (unrelated data I've 
replaced with "..."):

  <error type="UMR" desc="Uninitialized memory read (9 times)">
This is occurring while in thread 23611
Reading 8 bytes from 0x7fbfffe1c0 on the stack of thread 23611 (7 bytes at 
0x7fbfffe1c1 uninit)
Address 0x7fbfffe1c0 is      488 bytes below frame pointer in function 
_Unwind_RaiseException
    <stack>
      <frame func="*unknown func*" file="pc=0x3f68b0ecee"/>
      <frame func="_Unwind_RaiseException" file="/lib64/libgcc_s.so.1"/>
      <frame func="__cxa_throw" file="/usr/lib64/libstdc++.so.6"/>
      <frame func="FIX::Dictionary::getDay(std::string<char, 
std::char_traits<char>, std::allocator<char>> const&) const" 
file="/.../quickfix/1.12.4/src/src/C++/Dictionary.cpp" line="110"/>
      <frame func="FIX::SessionFactory::create(FIX::SessionID const&, 
FIX::Dictionary const&)" 
file="/.../quickfix/1.12.4/src/src/C++/SessionFactory.cpp" line="103"/>
      ...
      <frame func="__libc_start_main" file="/lib64/tls/libc.so.6"/>
      <frame func="_start" file="/usr/lib64/crt1.o"/>
    </stack>
  </error>

Does anyone know why this is reported and how it can be avoided, if possible 
at all?

The "tricky" point is that I set values for START_TIME/END_TIME and do not 
set anything for START_DAY/END_DAY, in the 'settings' Dicionary passed into 
SessionFactor::create().
If I set START_DAY/END_DAY too, there is no UMR because ConfigError isn't 
thrown in this case.

Any help is very appreciated!

Thanks in advance,
Igor 

Re: [Quickfix-developers] Error using PostgreSQL 8.2 - fatal errorLNK1104: cannot open file 'libpqdll.lib'

[Sean K. <sea...@pi...>]

We haven't had that specific problem.  But we have been having trouble
linking our app since we started evaluating upgrading to Postgres 8.2.
Unfortunately, another piece that seems to be playing a role here is our
use of STLport 4.6.2.  Anyone able to build with these two support
libraries on RHEL 3?


-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Djalma Rosa dos Santos Filho
Sent: Friday, April 13, 2007 10:19 AM
To: qui...@li...
Subject: [Quickfix-developers] Error using PostgreSQL 8.2 - fatal
errorLNK1104: cannot open file 'libpqdll.lib'

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



Disclaimer: Any references to Pipeline performance contained herein are =
based on historic performance levels which Pipeline expects to maintain =
or exceed but nevertheless does not guarantee. Congested networks, price =
volatility, or other extraordinary events may impede future trading =
activities and degrade performance statistics.

[Quickfix-developers] Error using PostgreSQL 8.2 - fatal error LNK1104: cannot open file 'libpqdll.lib'

[Djalma R. d. S. F. <drs...@gm...>]

Hello,

Trying to use PostgreSQL 8.2 with quickfix, I got the following link error:

fatal error LNK1104: cannot open file 'libpqdll.lib'

I only succeeded after modifying the source code to link with existing
libpq.lib.

Does anyone know if libpqdll was deprecated?

Regards,
Djalma

--> PostgreSQLConnection.h
...
#ifdef _MSC_VER
#pragma warning( disable : 4503 4355 4786 4290 )
//#pragma comment( lib, "libpqdll" ) // removed!
#pragma comment( lib, "libpq" ) // this one works!!
#endif
...

[Quickfix-developers] Repeated resend requests

[cstrader <cst...@cs...>]

I seem to have gotten into a loop where the QuickFix host is sending =
hundreds of repeated resend requests.  Logging off and on doesn't help.  =
Is there a way to reset to stop this?

thanks

[Quickfix-developers] VSTO and quickfix

[Axel <nj...@fa...>]

Hi.

I am trying to use quickfix with VSTO SE, but excel 2003 keeps crashing 
when the connection is opened. If I try the same code in a standalone 
application, everything works perfectly.

I'm able to create all the objects and the configuration is read 
successfully. When I call myapp.start() I don't get any exceptions, but 
when the socket is opened and connected, excel crashes (after my block 
of code is finished).

Does anyone have any idea what I'm doing wrong?

I've tried to connect to a jabberserver manually from the same project 
just to see if it's a problem with sockets but I'm able to 
connect/read/write without any problems when using the jabberserver.


-- 
Axel

Re: [Quickfix-developers] quickfix & delphi

[Djalma R. d. S. F. <drs...@gm...>]

Hi Abel / Stefano,

It is possible to simulate classes in pure C by implementing structs with
function pointers.
Of course, in this situation some  global  variables and
initialization/unitialization functions are required.
See Winamp SDK samples, they do exactly that and the plugins can be written
and tested in Delphi (I read that somewhere when I was investigating a good
plugin architecture for my current application).

IMHO, it would be much easier to create a COM wrapper (DLL - inproc) for
Quickfix using ATL.
An example is MSXML, you can use it in Delphi and looks like OOP.

Djalma

On 3/27/07, Kline - Facchetti Stefano <s.f...@kl...> wrote:
>
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
>  Abel,
> It's not possible to make a C++ wrapper, in fact delphi VCL can load
> external procedure/function from only pure C dll.
> As workaround I have make a C wrapper with only static method and pointer
> (in pure C is not possible to use class), and I use them to interface
> quickfixlib object..
>
> If you can use Delphi .NET I suggest to use it.
>
> Abel Monroy ha scritto:
>
> Ciao Stefano,
>
> This wrapper solution is the one that we are thinking of now, but we are
> kind of lost here. Do you take the quickfix.lib library and make some C++
> classes in order to make the calls to the different classes and functions?
> You say a C wrapper, so, do you think that it's not possible to make a C++
> wrapper? I'm asking this because QuickFix everything is classes, so I can't
> imagine how you can make this wrapper without using classes (do you define a
> bunch of singleton or static objects, in order to be able to call the
> methods inside the classes? )
> Thanks in advance
> Abel
>
> Kline - Facchetti Stefano wrote:
>
> Hi Abel,
> I use quickfix with Delphi 6.. for do it, I write a C wrapper to quickfix
> lib and compile it into a dll..
> >From Delphi I use call to wrapper dll.. and all work ok..
>
> Stefano
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

Re: [Quickfix-developers] quickfix & delphi

[Kline - F. S. <s.f...@kl...>]

Abel,
It's not possible to make a C++ wrapper, in fact delphi VCL can load 
external procedure/function from only pure C dll.
As workaround I have make a C wrapper with only static method and 
pointer (in pure C is not possible to use class), and I use them to 
interface quickfixlib object..

If you can use Delphi .NET I suggest to use it.

Abel Monroy ha scritto:
> Ciao Stefano,
>
> This wrapper solution is the one that we are thinking of now, but we 
> are kind of lost here. Do you take the quickfix.lib library and make 
> some C++ classes in order to make the calls to the different classes 
> and functions?
> You say a C wrapper, so, do you think that it's not possible to make a 
> C++ wrapper? I'm asking this because QuickFix everything is classes, 
> so I can't imagine how you can make this wrapper without using classes 
> (do you define a bunch of singleton or static objects, in order to be 
> able to call the methods inside the classes? )
> Thanks in advance
> Abel
>
> Kline - Facchetti Stefano wrote:
>> Hi Abel,
>> I use quickfix with Delphi 6.. for do it, I write a C wrapper to 
>> quickfix lib and compile it into a dll..
>> >From Delphi I use call to wrapper dll.. and all work ok..
>>
>> Stefano
>>

Re: [Quickfix-developers] quickfix & delphi

[Abel M. <am...@bo...>]

****************************** AVISO LEGAL =
******************************
La informaci=F3n contenida en este mensaje es para uso exclusivo de su =
destinatario. No debe copiarse, transmitirse a terceros ni guardarse por =
estos =FAltimos, salvo autorizaci=F3n del remitente.
Puede contener informaci=F3n confidencial o legalmente protegida cuyo =
r=E9gimen legal de utilizaci=F3n no se ve afectado por el hecho de que =
haya sido enviada por correo electr=F3nico.
Su env=EDo por error a una persona distinta de su destinatario real no =
implica que se haya modificado tal destinatario ni supone renuncia a su =
eventual car=E1cter confidencial o al r=E9gimen legal que rija su =
utilizaci=F3n.
Cualquier opini=F3n expresada en este mensaje vincular=E1 exclusivamente =
a la persona que lo haya remitido, excepto cuando el mensaje establezca =
lo contrario y el remitente est=E9 autorizado para establecer que dichas =
opiniones vincular=E1n a esta entidad.
En el supuesto de que este correo se recibiera por error, rogamos =
procedan a borrarlo, sin reenviarlo a terceros ni conservarlo en =
cualquier soporte y nos informen inmediatamente llamando al tel=E9fono =
34 91 7095566 o a la direcci=F3n de correo electr=F3nico remitente. =
Gracias.
****************************** DISCLAIMER ******************************
The information contained in this message is for the exclusive use of =
the named person. It can not be copied, transmitted to third parties or =
stored by the latter, except if authorised by the sender.
It may contain confidential or legally privileged information whose =
legal regime is not affected by the fact that this information has been =
sent by e-mail.=20
Its erroneous transmission to a person other than the real named person =
neither implies any modification of this named person nor a renunciation =
of the eventual confidentiality or legal regime affecting the use of =
concerned message.
Any views expressed in this message are binding exclusively upon the =
individual sender, except where the message states otherwise and the =
sender is authorised to bind this entity.=20
If you receive this message in error, please delete it without =
transmitting it to any third party or keeping it in any form and notify =
us immediately either by phone (34 91 7095566) or using the e- mail =
address of the sender. Thank You.

Re: [Quickfix-developers] quickfix & delphi

[Kline - F. S. <s.f...@kl...>]

Hi Abel,
I use quickfix with Delphi 6.. for do it, I write a C wrapper to 
quickfix lib and compile it into a dll..
 From Delphi I use call to wrapper dll.. and all work ok..

Stefano


Djalma Rosa dos Santos Filho ha scritto:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>   
>
> ------------------------------------------------------------------------
>
> Hi Abel,
>
> It is often difficult to interface native code which is compiled by 
> different compilers.
> Quickfix C++ lib exports functions with thiscall calling convension.
>
> I believe that it is not compatible with Delphi, as far as I know 
> Delphi prefers fastcall or stdcall.
> I worked with Delphi a long time ago (Delphi 4).  I had some 
> experience importing COM and C DLLs with stdcall and frankly I don't 
> believe that it is possible to use quickfix.lib in Delphi.
>
> I suggest that you go to managed code and import quickfix_net.dll and 
> quickfix_net_messages.dll in your Delphi projects.
>
> Djalma
>
> On 3/27/07, *Abel Monroy* <am...@bo... 
> <mailto:am...@bo...>> wrote:
>
>     QuickFIX Documentation:
>     http://www.quickfixengine.org/quickfix/doc/html/index.html
>     QuickFIX Support: http://www.quickfixengine.org/services.html
>
>     Hello everyone,
>
>     We have been using quickfix in our linux applications for a long time
>     and now we are trying to use it in our Windows apps. Someone has used
>     Delphi 2006 with QuickFix? We are having problems trying to  use the
>     .lib into Dephi projects, has anybody done this before or have
>     some idea
>     about what are the steps in order to get a Delphi application with
>     QuickFix?
>     Best Regards
>
>     Abel Monroy
>     Visual Trader
>
>
>
>
>     ****************************** AVISO LEGAL
>     ******************************
>     La información contenida en este mensaje es para uso exclusivo de
>     su destinatario. No debe copiarse, transmitirse a terceros ni
>     guardarse por estos últimos, salvo autorización del remitente.
>     Puede contener información confidencial o legalmente protegida
>     cuyo régimen legal de utilización no se ve afectado por el hecho
>     de que haya sido enviada por correo electrónico.
>     Su envío por error a una persona distinta de su destinatario real
>     no implica que se haya modificado tal destinatario ni supone
>     renuncia a su eventual carácter confidencial o al régimen legal
>     que rija su utilización.
>     Cualquier opinión expresada en este mensaje vinculará
>     exclusivamente a la persona que lo haya remitido, excepto cuando
>     el mensaje establezca lo contrario y el remitente esté autorizado
>     para establecer que dichas opiniones vincularán a esta entidad.
>     En el supuesto de que este correo se recibiera por error, rogamos
>     procedan a borrarlo, sin reenviarlo a terceros ni conservarlo en
>     cualquier soporte y nos informen inmediatamente llamando al
>     teléfono 34 91 7095566 o a la dirección de correo electrónico
>     remitente. Gracias.
>     ****************************** DISCLAIMER
>     ******************************
>     The information contained in this message is for the exclusive use
>     of the named person. It can not be copied, transmitted to third
>     parties or stored by the latter, except if authorised by the sender.
>     It may contain confidential or legally privileged information
>     whose legal regime is not affected by the fact that this
>     information has been sent by e-mail.
>     Its erroneous transmission to a person other than the real named
>     person neither implies any modification of this named person nor a
>     renunciation of the eventual confidentiality or legal regime
>     affecting the use of concerned message.
>     Any views expressed in this message are binding exclusively upon
>     the individual sender, except where the message states otherwise
>     and the sender is authorised to bind this entity.
>     If you receive this message in error, please delete it without
>     transmitting it to any third party or keeping it in any form and
>     notify us immediately either by phone (34 91 7095566) or using the
>     e- mail address of the sender. Thank You.
>
>     -------------------------------------------------------------------------
>     Take Surveys. Earn Cash. Influence the Future of IT
>     Join SourceForge.net's Techsay panel and you'll get the chance to
>     share your
>     opinions on IT & business topics through brief surveys-and earn cash
>     http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>     <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV>
>     _______________________________________________
>     Quickfix-developers mailing list
>     Qui...@li...
>     <mailto:Qui...@li...>
>     https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

-- 

Distinti saluti

Ing. Stefano Facchetti**

* *

*KLINE srl
*/Via Solferino, 4/b
25024 Leno (BS)
Tel. 030 9048384
Fax 02 700443977/**

* *

Questa e-mail, compreso qualunque allegato, può contenere informazione 
private o confidenziali. Se non siete il corretto destinatario o se 
avete ricevuto erroneamente questo messaggio contattate immediatamente 
il mittente e cancellate tutte le copie della e-mail. Se non siete il 
corretto destinatario non dovete riprodurre nessuna parte di questa 
e-mail o modificarne i contenuti. Questo messaggio rappresenta 
l'opinione del mittente e non necessariamente l'opinione dell'azienda.

This e-mail, including any attachments, may contain private or 
confidential information. If you think you may not be the intended 
recipient, or if you have received this e-mail in error, please contact 
the sender immediately and delete all copies of this e-mail. If you are 
not the intended recipient, you must not reproduce any part of this 
e-mail or disclose its contents to any other party. This message 
represents the opinion of the sender and not necessarily the opinion of 
the company.