⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 version_filters.hh

📁 xorp源码hg
💻 HH
字号:
// -*- c-basic-offset: 4; tab-width: 8; indent-tabs-mode: t -*-// vim:set sts=4 ts=8:// Copyright (c) 2001-2007 International Computer Science Institute//// Permission is hereby granted, free of charge, to any person obtaining a// copy of this software and associated documentation files (the "Software")// to deal in the Software without restriction, subject to the conditions// listed in the XORP LICENSE file. These conditions include: you must// preserve this copyright notice, and you cannot mention the copyright// holders in advertising related to the Software without their permission.// The Software is provided WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED. This// notice is a summary of the XORP LICENSE file; the license in that file is// legally binding.// $XORP: xorp/policy/backend/version_filters.hh,v 1.4 2007/02/16 22:47:00 pavlin Exp $#ifndef __POLICY_BACKEND_VERSION_FILTERS_HH__#define __POLICY_BACKEND_VERSION_FILTERS_HH__#include "policy_filters.hh"/** * @short Policy filters which support versioning [i.e. keep old version]. * * 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, * [null pointer] then give it 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 the reference count. * Say it's a normal route lookup and we do the filtering, and it results to * "accepted".  It doesn't imply we need to +1 the reference count. */class VersionFilters : public PolicyFilters {public:    VersionFilters();};#endif // __POLICY_BACKEND_VERSION_FILTERS_HH__

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -