model: Adding exclude filter processing in all content store implementations
Although exclude filter is honored now by content stores, forwarding
strategy is completely ignoring them. That is, if somebody replies to
an interest with a data packet that violates the filter, this data
packet will propagate back to the requester. This "problem" may or may
not be addressed in future.
Refs #1009 (http://redmine.named-data.net/issues/1009)
diff --git a/examples/custom-apps/ndn-api-app.cc b/examples/custom-apps/ndn-api-app.cc
index 3346b52..db55bb6 100644
--- a/examples/custom-apps/ndn-api-app.cc
+++ b/examples/custom-apps/ndn-api-app.cc
@@ -61,6 +61,10 @@
Ptr<Interest> interest = Create<Interest> ();
interest->SetName (m_name);
interest->SetInterestLifetime (m_interestLifetime);
+
+ Ptr<Exclude> exclude = Create<Exclude> ();
+ exclude->excludeOne (name::Component ("unique"));
+ interest->SetExclude (exclude);
m_face->ExpressInterest (interest,
MakeCallback (&ApiApp::GotData, this),
@@ -80,6 +84,7 @@
m_face = CreateObject<ApiFace> (GetNode ());
Simulator::Schedule (Seconds (1), &::ns3::ndn::ApiApp::RequestData, this);
+ Simulator::Schedule (Seconds (10), &::ns3::ndn::ApiApp::RequestData, this);
}
void