[omniORB] g3 and gif files

[Sai-Lai Lo]

Axel,

I think it is a myth that CORBA is by nature inefficent in handling bulk
data. One of the objective of the omniORB2 design is to squash this myth.

omniORB2 is very efficent in shipping sequence of integer types. There is
next to no marshalling or buffering overhead. So in Andrew's case, he can
easly create an interface with a single sendData method with a single in
argument of type sequence<octet>.

The 2MB maximum message size limit is arbitrary and can be changed to a
higher value if needed. This is purely a protection mechanism to limit
the amount of resource to commit on the server.


Sai-Lai


>>>>> Grohmann, Axel writes:

> andrew.brown@bt.com wrote:

>> Does anyone know how i would go about passing a .gif file and a .g3
>> file through a CORBA interface (specifically OMNIorb). Any information or
>> ideas on this would be much appreciated.
>> 
>> Thanks.
>> 
>> Andrew Brown.

>  Andrew,

> I am not sure whether it is a good idea to pass files (especially large
> files) via CORBA. OmniOrb uses a default maximum message size of 2 MB,
> and my impression is that any CORBA method invokation which passes more
> than, say 100 kB, is a misuse of CORBA.

> In our implementation, we separate between the control flow, i.e. information
> about the file being exchanged, and the data flow. The control flow is handled
> by CORBA, and the data flow is facilitated by either a distributed file system
> or FTP.



-- 
Sai-Lai Lo                                   S.Lo@uk.research.att.com
AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com 
24a Trumpington Street                Tel:   +44 223 343000
Cambridge CB2 1QA                     Fax:   +44 223 313542
ENGLAND