Re: [Quickfix-users] Peforming application-specific actions at creation of the initiator thread

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

Well, start() is really a convenience method.  What you should do if 
you want more control over the thread is to spawn one yourself and call 
block() on the initiator instead.  This will run the initiator entirely 
in one thread and give you control over code that is run at startup and 
wind down of that thread.

On Apr 26, 2004, at 3:17 AM, Igo...@ub... wrote:

>
> It is a requirement of our architecture that a database initialisation
> routine be called from each thread.
>
> But that aside, this looks like a more general requirement that some
> initialisation code needs to be executed at the beginning of the 
> thread.
>
>
> ------- Oren Miller <or...@qu...> -------
> Igor,
>
> What is the reason for needing to connect to your database in that
> thread?  Can't you just connect to it before you call start() on the
> initiator?
>
> --oren
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> http://www.thinkgeek.com/freeshipping/?cpg=12297
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>