quickfix-developers

[Quickfix-developers] Changing to ThreadedSocketAcceptor from SocketAcceptor

[Magnus B. <ber...@gm...>]

I have read quite a lot about the advantages of ThreadedSocketAcceptor over
SocketAcceptor.

I have an application that has been built with SocketAcceptor and
SocketInitiator, as we are currently getting more and more traffic, the
response time is getting slower and slower for users.

I understand that changing to the multi-threaded version would speed things
up, are there any obvious risks with this except having a thread-safe
application?

Could I basically just change my objects to the multi-threaded object and
start up without any unexpected behaviour from QuickFix?

Thanks,

Magnus Bergstrom
-- 
View this message in context: http://www.nabble.com/Changing-to-ThreadedSocketAcceptor-from-SocketAcceptor-tf4247490.html#a12087764
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] Changing to ThreadedSocketAcceptor from SocketAcceptor

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

On 8/10/07, Magnus Bergstrom <ber...@gm...> wrote:
>
>
> Could I basically just change my objects to the multi-threaded object and
> start up without any unexpected behaviour from QuickFix?



Thats the intent of the design.  It should just be a drop-in replacement.

Note also the SynchrnoizedApplication class.  This contains a mutex that is
locked before every call to your Application's to*/from* functions, making
for a crude but thread-safe Application when used in the multi-threaded
case.  This way you don't need to worry about locking your own data
structures, though you probably gain zero performance over the
single-threaded case and could even lose some.

-- 
Caleb Epstein

[Quickfix-developers] ThreadedSocketInitiator/ SynchronizedApplication vs SocketInitiator/ SynchronizedApplication

[Naveed A. <na...@nc...>]

Hello All,

I am using an initiator (ThreadedSocketInitiator/Application) to connect
to an Acceptor (ThreadedSocketAcceptor/Application).
This acceptor accepts connection from various initiators.
The initiator just connects to this acceptor.

What can be a better alternate if any in terms of the application
architecture is concerned...

For the Initiator
1. Should I use ThreadedSocketInitiator and SynchronizedApplication..?
2. Should I use SocketInitiator and SynchronizedApplication..?
3. Should I use SocketInitiator and Application..?
4. Should I use ThreadedSocketInitiator and Application..?

For the Acceptor
1. Should I use ThreadedSocketAcceptor and SynchronizedApplication..?
2. Should I use SocketAcceptor and SynchronizedApplication..?
3. Should I use SocketAcceptor and Application..?
4. Should I use ThreadedSocketAcceptor and Application..?


Thanks in Advance
-Naveed