\hypertarget{classVersionFilters}{
\section{VersionFilters Class Reference}
\label{classVersionFilters}\index{VersionFilters@{VersionFilters}}
}


Policy filters which support versioning \mbox{[}i.e.  




{\ttfamily \#include $<$version\_\-filters.hh$>$}

Inheritance diagram for VersionFilters:\begin{figure}[H]
\begin{center}
\leavevmode
\includegraphics[height=3.000000cm]{classVersionFilters}
\end{center}
\end{figure}


\subsection{Detailed Description}
Policy filters which support versioning \mbox{[}i.e. keep old version\mbox{]}.

The idea is to create a new policy filter on each configuration. Whenever a route is being processed, you read which filter to run. If this filter is 0, \mbox{[}null pointer\mbox{]} then give it \hyperlink{protocolthe-p}{the} last configuration. Else just run whatever filter is returned.

Filters should be referenced counted by routes. When reference count reaches 0, it should be deleted.

Why not keep filters internally here and read a filter id from route? Well because we cannot assume when to increment and decrement \hyperlink{protocolthe-p}{the} reference count. Say it's a normal route lookup and we do \hyperlink{protocolthe-p}{the} filtering, and it results to \char`\"{}accepted\char`\"{}. It doesn't imply we need to +1 \hyperlink{protocolthe-p}{the} reference count. 

The documentation for this class was generated from the following files:\begin{DoxyCompactItemize}
\item 
/home/greearb/git/xorp.ct.github/xorp/policy/backend/version\_\-filters.hh\item 
/home/greearb/git/xorp.ct.github/xorp/policy/backend/version\_\-filters.cc\end{DoxyCompactItemize}
