
Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.93]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id l41FmsY28187 for <dtn-users@mailman.dtnrg.org>; Tue, 1 May 2007 08:48:54 -0700
Received: from [192.168.1.2] (dsl081-061-178.sfo1.dsl.speakeasy.net [64.81.61.178]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.1/8.13.5) with ESMTP id l41FmqIe005364 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 1 May 2007 08:48:53 -0700 (PDT)
In-Reply-To: <f0d10dd60705010742x7607d793pb8f5ef40b536e855@mail.gmail.com>
References: <f0d10dd60705010742x7607d793pb8f5ef40b536e855@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E04FBDC0-A7C3-41DD-B839-78B3113B10F6@cs.berkeley.edu>
Content-Transfer-Encoding: 7bit
From: Michael Demmer <demmer@cs.berkeley.edu>
Subject: Re: [dtn-users] DTN_MAX_BUNDLE_MEM hard limit??
X-Applemailsentby: demmer
Date: Tue, 1 May 2007 08:48:57 -0700
To: dtn-users@mailman.dtnrg.org
X-Mailer: Apple Mail (2.752.3)
Sender: dtn-users-admin@mailman.dtnrg.org
Errors-To: dtn-users-admin@mailman.dtnrg.org
X-BeenThere: dtn-users@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: dtn-users@mailman.dtnrg.org
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=unsubscribe>
List-Id: discussion/answers list for users of the dtn reference implementation <dtn-users.mailman.dtnrg.org>
List-Post: <mailto:dtn-users@mailman.dtnrg.org>
List-Help: <mailto:dtn-users-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=subscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-users/>

The DTN_MAX_BUNDLE_MEM is only used for the API and is used to keep  
the RPC protocol for the dtnapi simple. 50K is basically arbitrary  
but it needs some limit.

When you're running within the routing layer, you can obviously use  
the BundlePayload class API to fill in the bundle, which has no hard  
size constraints, but will itself keep bundle data in the file.

Applications can use bigger bundles of course but then they need to  
use the file-based mechanism for passing bundles to and from the daemon.

I've been mulling over this issue for a while and am leaning towards  
maybe changing dtn_recv to be able to return the payload in chunks  
for the case where the user wants it in memory. That would make the  
api a bit easier to use I think.

-mike

On May 1, 2007, at 7:42 AM, Zahir Koradia wrote:

> Hi Mike,
> Is there any particular reason to have this value set to 50K? Are  
> there any dependencies on this figure anywhere? If I filled a  
> payload at the routing layer (bypassing dtn api) of size larger  
> than 50K(I am looking at around 2MB) and then sent it out would  
> there be any issues?
>
> Thanks,
> Zahir



Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.227]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id l41EgBY27803 for <dtn-users@mailman.dtnrg.org>; Tue, 1 May 2007 07:42:11 -0700
Received: by qb-out-0506.google.com with SMTP id a16so7704706qbd for <dtn-users@mailman.dtnrg.org>; Tue, 01 May 2007 07:42:10 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=DvUbpTrHHUmgsqY8P9TPUIX+67NsI/m1wXCWs/HW8uS9FllDmPivIrPd5Q3PjV2k+dylY06SCeQUA6xmwP2JwhkJtlGOD9U29DKiqOTHhvAYviDR/ORxtaFM1LqGjtvO1atK+Rlnl6WqEa4dkHXuyqAIm0iRqz/wML/4eqDaXE4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=lucxshftiD7hDXQRbfgeOtx7cbkNntuJTfgYG7asun3kUl6iwyU3WPsujuqBqc6/K3jikzL/kBHw55zQJJHuCYrbi+ot6o0yQOd3m26ToxtvXB6pPdBACsACT5TYifMPjNxfYMbYI2h8+9yTdc4AbhV2taq95ip4ZoEVOvKphWg=
Received: by 10.70.46.1 with SMTP id t1mr13405561wxt.1178030530150; Tue, 01 May 2007 07:42:10 -0700 (PDT)
Received: by 10.70.10.17 with HTTP; Tue, 1 May 2007 07:42:10 -0700 (PDT)
Message-ID: <f0d10dd60705010742x7607d793pb8f5ef40b536e855@mail.gmail.com>
Date: Wed, 2 May 2007 01:42:10 +1100
From: "Zahir Koradia" <zahir.koradia@gmail.com>
To: dtn-users@mailman.dtnrg.org
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_77530_29947147.1178030530073"
Subject: [dtn-users] DTN_MAX_BUNDLE_MEM hard limit??
Sender: dtn-users-admin@mailman.dtnrg.org
Errors-To: dtn-users-admin@mailman.dtnrg.org
X-BeenThere: dtn-users@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: dtn-users@mailman.dtnrg.org
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=unsubscribe>
List-Id: discussion/answers list for users of the dtn reference implementation <dtn-users.mailman.dtnrg.org>
List-Post: <mailto:dtn-users@mailman.dtnrg.org>
List-Help: <mailto:dtn-users-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=subscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-users/>

------=_Part_77530_29947147.1178030530073
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Mike,
Is there any particular reason to have this value set to 50K? Are there any
dependencies on this figure anywhere? If I filled a payload at the routing
layer (bypassing dtn api) of size larger than 50K(I am looking at around
2MB) and then sent it out would there be any issues?

Thanks,
Zahir

------=_Part_77530_29947147.1178030530073
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Mike,<br>Is there any particular reason to have this value set to 50K? Are there any dependencies on this figure anywhere? If I filled a payload at the routing layer (bypassing dtn api) of size larger than 50K(I am looking at around 2MB) and then sent it out would there be any issues?
<br><br>Thanks,<br>Zahir<br>

------=_Part_77530_29947147.1178030530073--

