Re: [PATCH] New function to deduce ORB capability

[Jules Colding <colding omesc com>]

Hi,

On Wed, 2006-04-05 at 08:05 +0800, KC wrote:
> Export API, ORBit_get_giop_recv_limit(), is GOOD and
> necessary for large data stream transfer.

Agreed.

> However, why not simply hide this limit inside internal
> implementation ?   And let both stub/skeleton code
> handle the fragment automatically ?
> 
> I don't know how difficult it will be, just think that should be
> more reasonable from end user's point of view.
> 
> IMHO, the size limit should only affect ORB's performance,
> and should be invisible from client.   It is system
> administrator's task to deices how big the size limit should be
> instead of the client writer.

The limit seems to be very intentionally introduced to prevent DOS type
attacks. There is no such limit for outgoing data. The rationale seems
to be that the client has full control over the amount of data that are
outgoing but has no control over the amount of incoming data.

I therefore think that it is better to make the client application
intentionally accept large incoming data streams instead of hiding the,
in many ways, artificial loop over the incoming data chunks inside the
stub/skeleton code.


Best regards,
  jules