Thread: Re: [Quickfix-developers] VB.NET
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: <OM...@th...> - 2003-01-10 22:20:54
|
Well I think we basically need to come up with a new namespace. I can send you what was sent to me (although I'm not sure what version it is based off of). John is using the namespace FixDotNet, but I'm thinking of going with QuickFIX or something (more like the java api). --oren |---------+-----------------------------------------------> | | "Rob Kulseth" <ro...@ri...> | | | Sent by: | | | qui...@li...ur| | | ceforge.net | | | | | | | | | 01/10/2003 11:32 AM | | | | |---------+-----------------------------------------------> >----------------------------------------------------------------------------------------------| | | | To: <qui...@li...> | | cc: | | Subject: [Quickfix-developers] VB.NET | >----------------------------------------------------------------------------------------------| Are there plans to make a change to the standard QuickFix Code to make it useable in VB.NET, or should this change be done ourselves. Thanks Rob Kulseth ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Rob K. <ro...@ri...> - 2003-01-10 22:34:33
|
I have made the changes using the namespace "FixNet" in my copy of quick = fix. The change was easy to make. All I did was search for the text = "Fix::" and replace it with "FixNet::" and change all the namespace = statements to read "namespace FixNet". This appears to be working fine. = If you guys decide to make a standard namespace change, it shouldn't be = very hard to change on my Code to match. Are there any other known = VB.net issues? Thanks for all your help Rob Kulseth -----Original Message----- From: OM...@th... [mailto:OM...@th...] Sent: Friday, January 10, 2003 4:21 PM To: Rob Kulseth Cc: qui...@li...; qui...@li... Subject: Re: [Quickfix-developers] VB.NET Well I think we basically need to come up with a new namespace. I can = send you what was sent to me (although I'm not sure what version it is based = off of). John is using the namespace FixDotNet, but I'm thinking of going = with QuickFIX or something (more like the java api). --oren |---------+-----------------------------------------------> | | "Rob Kulseth" <ro...@ri...> | | | Sent by: | | | qui...@li...ur| | | ceforge.net | | | | | | | | | 01/10/2003 11:32 AM | | | | |---------+-----------------------------------------------> = >------------------------------------------------------------------------= ----------------------| | = | | To: <qui...@li...> = | | cc: = | | Subject: [Quickfix-developers] VB.NET = | = >------------------------------------------------------------------------= ----------------------| Are there plans to make a change to the standard QuickFix Code to make = it useable in VB.NET, or should this change be done ourselves. Thanks Rob Kulseth ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See! http://www.vasoftware.com _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Vitor C. <vc...@hi...> - 2003-01-13 14:53:01
|
I've had some other problems with .Net but not exclusively with VB. If you create any managed components in .Net and try to expose them as COM objects you will have some problems. This has to do, to the extent of my knowledge, with a bug in the VC++ compiler in the current version of Visual Studio regarding the calling of unmanaged code from managed code. Nonetheless I've compiled both QuickFix and some managed components done with C# and afterwards exposed them as COM components with the Beta 2 of Visual Studio 2003 (codenamed Everett) and all worked fine. So the bug gets fixed in the next Visual Studio version. Regards Vitor Castro -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Rob Kulseth Sent: sexta-feira, 10 de Janeiro de 2003 22:34 To: qui...@li... Subject: RE: [Quickfix-developers] VB.NET I have made the changes using the namespace "FixNet" in my copy of quick fix. The change was easy to make. All I did was search for the text "Fix::" and replace it with "FixNet::" and change all the namespace statements to read "namespace FixNet". This appears to be working fine. If you guys decide to make a standard namespace change, it shouldn't be very hard to change on my Code to match. Are there any other known VB.net issues? Thanks for all your help Rob Kulseth -----Original Message----- From: OM...@th... [mailto:OM...@th...] Sent: Friday, January 10, 2003 4:21 PM To: Rob Kulseth Cc: qui...@li...; qui...@li... Subject: Re: [Quickfix-developers] VB.NET Well I think we basically need to come up with a new namespace. I can send you what was sent to me (although I'm not sure what version it is based off of). John is using the namespace FixDotNet, but I'm thinking of going with QuickFIX or something (more like the java api). --oren |---------+-----------------------------------------------> | | "Rob Kulseth" <ro...@ri...> | | | Sent by: | | | qui...@li...ur| | | ceforge.net | | | | | | | | | 01/10/2003 11:32 AM | | | | |---------+-----------------------------------------------> >----------------------------------------------------------------------- -----------------------| | | | To: <qui...@li...> | | cc: | | Subject: [Quickfix-developers] VB.NET | >----------------------------------------------------------------------- -----------------------| Are there plans to make a change to the standard QuickFix Code to make it useable in VB.NET, or should this change be done ourselves. Thanks Rob Kulseth ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Gene G. <mus...@ya...> - 2003-01-28 18:05:11
|
Quickfix 1.3.2 has a following problem: when the port specified for acceptor is already taken (for example FIX server is started erroneously twice), acceptor fails, but gives no indication to of that to the host program. Acceptor (both ST and MT) "start" method still returns true as if application has shut down normally, and no Application method is called to indicate that something is wrong. Since thread that executes Application->onRun does not exit on user action (as is normally the case), and no indication is given to program that something is wrong, this behavior usually results in an unpleasant situtaion such as deadlock (when thread_join is attempted with never-exiting onRun), or a crash (on my Linux due to a libpthread bug thread_join returns fine, but onRun is still executing and crashes when application class is cleaned up) Although there is nothing that FIX engine can do to stop onRun thread by itself, it should somehow indicate to the host program that the acceptor failed to initiate the accepting socket. Returning "false" from the start method would allow the developers to clean up onRun themselves. Fixing return value of the start method will require small modifications to SocketAccepor::onStart, and ThreadedSocketAcceptor::onStart; if the blocking call (SocketServer->block or socket_accept) fails, the whole method should return false. Gene __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X