[Ndn-interest] Parameter, argument passing in Interest name

Muhammad Hosain Abdollahi Sabet M.AbdollahiSabet at mail.sbu.ac.ir
Mon May 11 12:04:01 PDT 2015


Oops .I'm sorry. I hadn't seen the other answers. Yes. That could be a solution in cases like passing a parameter. Also there could be some encryption policies for applications, so that sent parameters wouldn't be clear text.

Thanks,
Sabet


-----Original Message-----
From: Ndn-interest on behalf of Tai-Lin Chu
Sent: Mon 5/11/2015 11:23 PM
To: Gusev, Peter
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Parameter, argument passing in Interest name
 
There is discussion about markedComponent, which will be a
better/standardized way to do this.

I think Peter's method is the "current" best practice, but the
application should figure out the canonical form of those params.

On Mon, May 11, 2015 at 11:38 AM, Gusev, Peter <peter at remap.ucla.edu> wrote:
> No, I meant producer.
> As your producer registers only prefix
> /ndn/edu/ucla/remap/some_app/something it will inevitably receive any
> interests that have this prefix AND any kind of suffix
> /ndn/edu/ucla/remap/some_app/something/<could_be_anything_here> in the
> interests' name.
>
> Thus, producer should carefully filter unwanted interests and check whether
> interest name it received has a meaningful components after the base prefix
> (i.e. for the previous example - check whether it has 6 components with
> names arg1 arg2 arg3 and values accordingly).
>
> As far as I know, there's no such thing as REST-like arguments supported by
> the protocol right now.
>
> Thanks,
>
> --
> Peter Gusev
> Programmer/Analyst @ REMAP, UCLA
>
> peter at remap.ucla.edu
> +1 213 5872748
> peetonn_ (skype)
>
> On May 11, 2015, at 11:27 AM, Anil Jangam <anilj.mailing at gmail.com> wrote:
>
> Thanks Peter.. just to clarify.. when you said 1. "parse it on the producer
> side " and 2. "your producer should be aware of that" you actually meant to
> say Consumer, right? This basically means, I will have to design my
> application namespace carefully to accommodate such extensions, and its
> completely application level details.
>
> I was curious if protocol itself offers anything (so I just use an API) to
> set any user specific data into Interest, which ideally does the same thing
> as you mentioned.
>
> /anil.
>
>
> On Mon, May 11, 2015 at 11:13 AM, Gusev, Peter <peter at remap.ucla.edu> wrote:
>>
>> Hi Anil,
>>
>> I believe you can pass anything you like after the prefix your producer
>> has registered. Though you have to parse it on the producer side if it's
>> something more than just another few name components.
>>
>> I.e. your producer has registered prefix
>> /ndn/edu/ucla/remap/some_app/something that will make it receiving any
>> interests with this prefix, so you can send out interests like that
>> /ndn/edu/ucla/remap/some_app/something/arg1/10/arg2/20/arg3/30 and your
>> producer should be aware of that and treat name components that come after
>> the registered prefix accordingly.
>>
>> Thanks,
>>
>> --
>> Peter Gusev
>> Programmer/Analyst @ REMAP, UCLA
>>
>> peter at remap.ucla.edu
>> +1 213 5872748
>> peetonn_ (skype)
>>
>> On May 11, 2015, at 11:05 AM, Muhammad Hosain Abdollahi Sabet
>> <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
>>
>> Hi Anil,
>> The only way that I'm aware of, is kind of tricky. The parameter
>> sender(active producer?) sends an interest to a receiver(passive consumer).
>> The receiver responds to the interest and sends another interest. Finally
>> the sender pass parameter in a data packet in response to the latter.
>>
>> Thanks,
>> Sabet
>>
>>
>> -----Original Message-----
>> From: Ndn-interest on behalf of Anil Jangam
>> Sent: Mon 5/11/2015 10:23 PM
>> To: ndn-interest at lists.cs.ucla.edu
>> Subject: [Ndn-interest] Parameter, argument passing in Interest name
>>
>> Hi,
>>
>> I am trying to understand how I can pass a parameter using Interest
>> message
>> as a carrier. I want to exchange an application specific data between
>> producer and consumer.
>>
>> I believe some mechanism exist to pass argument in strategy URL using
>> '?id=1254' convention. Does something similar possible within Interest
>> name?
>>
>> /anil.
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>
>>
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>

_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150511/b8ee82e2/attachment.html>


More information about the Ndn-interest mailing list