[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5},"routes/user.$name.replies",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"replies",[34],"user",{"_20":21,"_13":14,"_22":23,"_24":14,"_25":26,"_27":28,"_29":30,"_31":16,"_32":33},"loginname","JerryShiJianWei","page",1,"limit",50,"total","id","18120","avatar_url","https://avatars.githubusercontent.com/u/12482635?v=3","githubUsername","create_at","2015-07-28 09:00:26.037","score",5,"topic_count",0,"reply_count","is_star",false,{"_20":35,"_36":37,"_38":-5,"_39":40,"_41":42,"_43":44,"_45":33,"_46":33,"_31":47,"_48":49,"_25":50,"_51":52},"7243","author_id","12155","tab","content","# 代码之外\r\n## 前言\r\n最近做项目, 需要用nodejs开发weixin的自动回复系统（包括菜单事件什么的, 在github上简单看了一些库, 发现都有一个类似的bug. 每当用户发送消息的时候, 微信服务器都会向我们的nodejs服务器发送一个POST请求, 包括 [node-wechat](https://github.com/nswbmw/node-wechat \"node-wechat\"), [weixin_api](https://github.com/JeremyWei/weixin_api \"weixin_api\"), [node-weixin](https://github.com/feeloc/node-weixin \"node-weixin\"), 在收到 POST 请求之后将请求的 response 设置在全局位置, 这样在多条消息同时到来的时候会有问题. 先来的消息很有可能会通过后面的 response 发送消息. \r\n这个问题我和 node-wechat 的作者 [nswbmw](https://github.com/nswbmw) 提出了, 他好心的要修改一下, 但是，我现在很立刻就需要呀~ 所以就自己动手了. \r\n写的时候也参考了文中提到的三个库的优缺点, 在此一并谢过~ 高级功能会在日后逐渐完善, 希望有好心人一起完整其他功能~\r\n## 注意事项\r\n- 有的时候同一条消息会触发多次，是因为在 5s 内，你的服务器没有给weixin服务器相应，weixin服务器会在未来的有限时间内不断的向你的服务器发送同一条消息的请求。可以通过 `MsgId` 来判断是否为同一条消息\r\n\r\n# Nodejs Wechat\r\n\r\n [![NPM version](https://badge.fury.io/js/nodejs-wechat.png)](http://badge.fury.io/js/nodejs-wechat) [![Build Status](https://travis-ci.org/idy/nodejs-wechat.svg?branch=master)](https://travis-ci.org/idy/nodejs-wechat)\r\n\r\nNodejs wrapper of wechat api\r\n\r\n### __Usage__\r\n#### Work with native http server\r\n```javascript\r\nvar http = require('http');\r\nvar xmlBodyParser = require('express-xml-parser');\r\nvar Wechat = require('nodejs-wechat');\r\n\r\nvar opt = {\r\n token: 'TOKEN',\r\n url: '/'\r\n};\r\nvar parse = xmlBodyParser({\r\n type: 'text/xml'\r\n});\r\nvar wechat = new Wechat(opt);\r\nwechat.on('event.subscribe', function(session) {\r\n session.replyTextMsg('欢迎您关注我们的订阅号');\r\n});\r\nvar server = http.createServer(function(req, res) {\r\n if (req.method === 'GET') {\r\n wechat.verifyRequest(req, res);\r\n } else {\r\n parse(req, res, function(err) {\r\n if (err) {\r\n res.end();\r\n return;\r\n }\r\n wechat.handleRequest(req, res);\r\n });\r\n }\r\n});\r\nserver.listen(80);\r\n```\r\n\r\n#### Work with express\r\n```javascript\r\nvar express = require('express');\r\nvar app = express();\r\nvar middlewares = require('express-middlewares-js');\r\napp.use('/weixin', middlewares.xmlBodyParser({\r\n type: 'text/xml'\r\n}));\r\n\r\n/*\r\n Alternative way\r\n\r\nvar xmlBodyParser = require('express-xml-parser');\r\napp.use('/weixin', xmlBodyParser({\r\n type: 'text/xml',\r\n limit: '1mb'\r\n}));\r\n\r\n*/\r\n\r\nvar Wechat = require('nodejs-wechat');\r\nvar opt = {\r\n token: token,\r\n url: '/weixin'\r\n};\r\nvar wechat = new Wechat(opt);\r\n\r\napp.get('/weixin', wechat.verifyRequest.bind(wechat));\r\napp.post('/weixin', wechat.handleRequest.bind(wechat));\r\n\r\n// you can also work with other restful routes\r\napp.use('/api', middlewares.bodyParser());\r\n\r\nwechat.on('text', function(session) {\r\n session.replyTextMsg('Hello World');\r\n});\r\nwechat.on('image', function(session) {\r\n session.replyNewsMsg([{\r\n Title: '新鲜事',\r\n Description: '点击查看今天的新鲜事',\r\n PicUrl: 'http://..',\r\n Url: 'http://..'\r\n }]);\r\n});\r\nwechat.on('voice', function(session) {\r\n session.replyMsg({\r\n Title: 'This is Music',\r\n MsgType: 'music',\r\n Description: 'Listen to this music and guess ths singer',\r\n MusicUrl: 'http://..',\r\n HQMusicUrl: 'http://..',\r\n ThumbMediaId: '..'\r\n });\r\n});\r\n\r\napp.listen(80);\r\n```\r\n\r\n> __NOTE__: We apply `{ type: 'text/xml' }` to `xmlBodyParser` as weixin server \r\nsend us a `text/xml` content type instead of `application/xml`.\r\n\r\n### __API__\r\n#### Wechat\r\n- `#verifyRequest(req, res)`\r\n > This is a express/connect middleware, which verify the signature of\r\n request from weixin server\r\n\r\n- `#handleRequest(req, res)`\r\n > This is a express/connect middleware, which handle the request post from \r\n weixin server\r\n\r\n- `#on(msgType, handler)`\r\n > Wechat is an inheritance from event.EventEmitter. Wechat will emit an event\r\n in incoming message's `MsgType`, with a `Session` as parameter. Valid events: \r\n >\r\n > `text`, `image`, `voice`, `video`, `location`, `link`, `event.subscribe`, \r\n `event.unsubscribe`, `event.SCAN`, `event.LOCATION`, `event.CLICK`, `event.VIEW`,\r\n `error`\r\n >\r\n > __References__: [接收普通消息](http://mp.weixin.qq.com/wiki/index.php?title=%E6%8E%A5%E6%94%B6%E6%99%AE%E9%80%9A%E6%B6%88%E6%81%AF \"接收普通消息\"), \r\n [接收事件推送](http://mp.weixin.qq.com/wiki/index.php?title=%E6%8E%A5%E6%94%B6%E4%BA%8B%E4%BB%B6%E6%8E%A8%E9%80%81 \"接收事件推送\")\r\n\r\n#### Session\r\n- `incomingMessage`\r\n > This is a direct parse of weixin server request\r\n\r\n```xml\r\n\r\n\r\n\r\n123456789\r\n\r\n\r\n\r\n```\r\nBecomes\r\n```json\r\n{\r\n \"ToUserName\": \"toUser\",\r\n \"FromUserName\": \"FromUser\",\r\n \"CreateTime\": \"123456789\",\r\n \"MsgType\": \"event\",\r\n \"Event\": \"subscribe\"\r\n}\r\n```\r\n\r\n- `req` \r\n > This is the request from weixin server\r\n\r\n- `res`\r\n > This is the response to weixin server\r\n\r\n- `#replyMsg(msgObject)`\r\n > Reply a message via `this.res`\r\n\r\n- `#replyTextMessage(content)`\r\n > Reply a text message\r\n\r\n- `#replyNewsMessage(articles)`\r\n > Reply a news messages.\r\n\r\n### TODO\r\n- Advanced interfaces\r\n > Will finish advanced interfaces before July/2014, welcome send pull requests :)","title","使用 NodeJs 响应微信请求","last_reply_at","2016-08-10 08:57:49.6","good","top",6,"visit_count",66545,"2014-05-19 03:05:32.468","author",{"_13":53,"_22":54},"idy","https://avatars.githubusercontent.com/u/687349?v=3"]