[omniORB] -ORBgiopMaxMsgSize (again)

[randy.shoup@tumbleweed.com]

henning.schmidt@philips.com wrote:
> 
> I know I can set the maximum message size through the startup parameter <-ORBgiopMaxMsgSize> or at runtime through <omniORB::MaxMessageSize()>
> 
> Now: if I want to transmit a string that is longer than the current <omniORB::MaxMessageSize>: can I just chop it up into pieces and transmit the complete information as a sequence<string>?
> 
> Same question in more general words: The size of which unit is finally affected by the <omniORB::MaxMessageSize>?
> - Is it the size of one element inside a complex type that I transmit?
> - Is it the size of one (arbitrarily complex) parameter (out of a couple that my function might have).
> - is it the total size of all parameters that my function takes?
> 

It is the total size of the CORBA request, which includes all your
parameters.

-- Randy
_________________________________________________________________  
Randy Shoup                                     (650)216-2038  
Senior Architect                                rshoup@tumbleweed.com  
Tumbleweed Communications Corporation