[Nfd-dev] Supporting objects larger than 8KB

[Junxiao Shi]

Hi Christos

Practical limit of NDN packet size is controlled by
ndn::MAX_NDN_PACKET_SIZE constant in ndn-cxx (common.hpp).
There shouldn't be hard-coded packet size limit anywhere else, otherwise
it's a bug.

You may change this constant, and recompile everything.

Yours, Junxiao
On Oct 29, 2014 12:42 PM, "Christos Papadopoulos" <christos at cs.colostate.edu>
wrote:

> I should have been more clear in my question.
>
> I was asking if there is a reason not to make it configurable.
> The answers I got offer wisdom about not exceeding size X when running
> over the big-I Internet.
>
> I want to separate the question of selecting the appropriate size and what
> NFD should support.
>
> If I have my private network where I want to support a large object size
> or even if I want to experiment with different sizes to try out different
> fragmentation algorithms, I should be able to do it, right?
>
> Hopefully the max object size is a configuration parameter somewhere and
> NFD does not make any assumptions.
>
> Maybe the answer is go ahead and try it and file a bug report if it breaks
> :-)
>
> Christos.
>
>
> On 10/28/2014 04:21 PM, Junxiao Shi wrote:
>
>> Hi Christos
>>
>> The 8800-octet practical packet size limit comes from CCNx.
>> I asked about the reason for this setting, and I agree with their
>> answer: http://www.ccnx.org/pipermail/ccnx-users/2013-October/001355.html
>>
>> Yours, Junxiao
>>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141029/9dd3ccdd/attachment.html>