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; } ?>javascript - Difference in history implementation by backbone.js, davis.js and history.js - Stack Overflow

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

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>javascript - Difference in history implementation by backbone.js, davis.js and history.js - Stack Overflow

    javascript - Difference in history implementation by backbone.js, davis.js and history.js - Stack Overflow

    programmeradmin2浏览0评论

    All these 3 libraries allow to manipulate history object. OK, backbone does a lot of more but let consider only it history part.

    • .js
    • .js

    What is a difference between these 3 implementation?

    All these 3 libraries allow to manipulate history object. OK, backbone does a lot of more but let consider only it history part.

    • http://documentcloud.github./backbone/#History
    • https://github./olivernn/davis.js
    • https://github./browserstate/history.js

    What is a difference between these 3 implementation?

    • javascript
    • backbone.js
    • browser-history
    • history.js
    Share Improve this question edited Jun 30, 2013 at 19:37 balupton 48.7k32 gold badges134 silver badges184 bronze badges asked Dec 1, 2011 at 23:11 Wojciech BednarskiWojciech Bednarski 6,3739 gold badges50 silver badges75 bronze badges
    Add a ment  | 

    2 Answers 2

    Reset to default 15

    History.js is more of a polyfil for browsers that do not natively support HTML5 pushState and for ironing out the differences between different browser implementations of pushState.

    Davis.js is a routing layer, primarily on top of pushState (although this can be switched out easily to hash routing). It gives you a simple api to define and respond to routes within your application.

    Backbone's router is similar to Davis, however it tries to automatically fall back to hash based routing when pushState is not available.

    As the author of Davis I'm slightly biased but I think the Davis api is slightly nicer and more powerful than backbones. I also think that trying to gracefully handle falling back to hash based routing when pushState is not available is not worth the effort and plexity that it can introduce.

    Here you go:

    • davis.js only supports HTML5 history.pushState. Browsers that don't work with it are not supported, so probably not an option.
    • Both backbone and history.js have fallbacks to onhashchange.
    • As you know already backbone also does MVC and through underscore on which it depends gives you additional helpers for functional stuff.

    It really depends on whether you need the additional Backbone functionality in which case it's an obvious choice.

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论