[prev in list] [next in list] [prev in thread] [next in thread] 

List:       omniorb-list
Subject:    Re: [omniORB] transports
From:       "Renzo Tomaselli" <renzo.tomaselli () tecnotp ! it>
Date:       2004-07-22 7:21:57
Message-ID: 005601c46fbc$948f2380$0100a8c0 () Renzo
[Download RAW message or body]

Oops ! I missed the point that component tags are added only at
initialization time, according to configured end points.
Sorry for wasting bandwidth,

Renzo

----- Original Message ----- 
From: "Renzo Tomaselli" <renzo.tomaselli@tecnotp.it>
To: "Omniorb list" <omniorb-list@omniorb-support.com>
Sent: Tuesday, July 20, 2004 4:06 PM
Subject: [omniORB] transports


> Hi all,
>     I'm adding my own transport to OmniORB 4.03 for security reasons.
> I have a question, though: in ior.cc, we have a couple of static sequence
> arrays named my_alternative_addr and my_ssl_addr.
> They cover related needs for adding profiles for multiple tcp addresses
and
> ssl.
> But they increase their length each time a new ior has to include related
> component profiles, in add_TAG_ALTERNATE_IIOP_ADDRESS and
> add_TAG_SSL_SEC_TRANS.
> Then the ior is finally assembled by a proper interceptor in
> insertSupportedComponents().
> Fine, but when are those sequences reset to a zero length ? Never, as far
as
> I could see.
> This lead me thinking that in those two cases we should have components
grow
> up indefinetely as long as new iors are built.
> Where is the trick ?
> Thanks,
>
> Renzo Tomaselli
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list@omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>


_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
[prev in list] [next in list] [prev in thread] [next in thread]