[omniORB] Problem with giopMaxMsgSize

[Visscher, Bruce]

John,

(Anyone who knows better: feel free if any of this is inaccurate since
I am still dealing with legacy versions of omniORB for the most part...)

> It works, but if omniORB has a bug, I'm sure you guys would like to know.

This is not a bug.  The parameter is spelled giopMaxMsgSize and it goes
in your configuration file (see sample.cfg).

Alternatively, since it looks like you are running Windows it can also
go in your Windows registry.  See sample.reg.

The maximum is there to protect servers from rogue clients but 2MB can
be small depending on your application.

(It used to be that you could override this programatically. Is this still
true?)

Bruce

-----------------------------------------
CONFIDENTIALITY NOTE:  This e-mail message, including any  attachment(s),
contains information that may be confidential,  protected by the attorney-
client or other legal privileges, and/or  proprietary non-public
information.  If you are not an intended  recipient of this message or an
authorized assistant to an intended  recipient, please notify the sender by
replying to this message and  then delete it from your system.  Use,
dissemination, distribution,  or reproduction of this message and/or any of
its attachments (if  any) by unintended recipients is not authorized and
may be unlawful.