AW: [omniORB] omniORB 4 Options

[Thierry DESCOMBES]

Sorry, I badly expressed myself :
I know how to call orb_init, but it seems that some of this options are 
incompatible together. Is somebody has noticed something similar ? (I'm 
using OmniORB 4.0.0)
(The deconnection of my client is taken into account if I use only 
clientCallTimeOutPeriod, but not when I use all this options).

Thanks.

At 15:18 28/07/2003 +0200, Barthel Marco (MPA/DS) wrote:
> > It seems that if you call orb_init with all the following
> > options, they
> > aren't all taken into account... Do I make something wrong ?
> >                             { "-ORBclientCallTimeOutPeriod",
> > "1000",       \
> >                             "-ORBserverCallTimeOutPeriod",
> > "1000",       \
> >                             "-ORBinConScanPeriod", "1",
> >       \
> >                             "-ORBoutConScanPeriod","1" }
>
>If you want to use it as an replacement for argc, argv you are right.
>
>If you want to use it as the omniORB specific options parameter in
>CORBA::ORB_init you must use the following without "-ORB"
>
>const char* options[][2] =
>{
>  {"clientCallTimeOutPeriod", "1000"},
>  {"serverCallTimeOutPeriod", "1000"},
>  {"inConScanPeriod", "1"},
>  {"outConScanPeriod","1"},
>  {0,0}
>};
>
>CORBA::ORB_init(argc, argv, "omniORB4", options);
>
>you need  {0,0} because there is no argc (argument count) for the options
>parameter.
>
>
>
>see omniORB 4.0 User's Guide page 41 (Chapter 4 omniORB configuration and
>API) for more info.
>
>-marco
>
>_______________________________________________
>omniORB-list mailing list
>omniORB-list at omniorb-support.com
>http://www.omniorb-support.com/mailman/listinfo/omniorb-list