te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>Canonical XML 2.0 with Namespace PrefixRewrite - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>Canonical XML 2.0 with Namespace PrefixRewrite - Stack Overflow

    Canonical XML 2.0 with Namespace PrefixRewrite - Stack Overflow

    programmeradmin3浏览0评论

    I'm writing a Nuget Package (which I'll post as Open Source to Github once it's done) that implements xml canonicalization using the Canonical XML Version 2.0 (c14n2) spec. I've also been using Test cases for Canonical XML 2.0 test data to write unit tests for my application.

    I found what I believe to be an error in one of the test cases for the scenario of re-writing prefixes during canonicalization. The expected value results in invalid xml. The test case is for 3.2 Default namespace declarations.

    Here is the original xml to be canonicalized:

    <foo xmlns:a="http://a" xmlns:b="http://b">
 <b:bar b:att1="val" att2="val"/>
</foo>

    After applying prefix rewriting, the expected xml for the "After c14n with PrefixRewrite" test case is the xml below (which is invalid xml since you cannot have a qualified namespace with an empty uri):

    <n0:foo xmlns:n0="">
 <n1:bar xmlns:n1="http://b" att2="val" n1:att1="val"></n1:bar>
</n0:foo>

    I sent an email to the W3C public-xmlsec mailing list ([email protected]), but haven't been able to reach anyone so far. Is anyone familiar with the spec or have any ideas on a technical solution?

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论