phodal/iot-coap

IoT Learning with CoAP Protocol

iot-coap's Issues

TODO

#2014-09-03 的分格线

后续有真实硬件设备后需要增加调整的功能：
1）"key":[
"id",
"value",
"sensors1",
"sensors2"
],
应该改为
"key":[
"id",
"sensor",
"value",
"binary"
],
restful 格式为 coap://127.0.0.1/v1/id/1/sensor/2/value/{json}
或者 coap://127.0.0.1/v1/id/1/sensor/2/binary/{...bin}
2)上面的{}里面的内容必须包含两个键值，一个时间戳，一个数据
3) 客户端支持 highchart 来生成实时曲线
4)数据库要调整，大家多讨论讨论
index[primary key], id, sensor, value_ts, value_data

#2014-09-11 的分格线

1. POST /v1/id/:id 创建设备
2. PUT /v1/id/:id 编辑设备
3. GET /v1/id/:id 查看设备
4. DELETE /v1/id/:id 删除设备
5. GET /v1/id/ 罗列设备
   6）除开第4没有参数，1,2,3的参数为
   {
   "name":"foo",
   "desc":"test foo",
   "local":"SHENZHEN",
   "latitude":114.07,
   "longitude":22.33
   }
6. 设备信息专门用一个数据库，方便后期地图使用，格式为
   id integer primary key, name text, dest text, local text, latitude real, longitude real

#2014-09-12 的分格线

1. POST /v1/id/:id/ch/:ch 创建通道
2. PUT /v1/id/:id/ch/:ch 编辑通道
3. GET /v1/id/:id/ch/:ch 查看通道
4. DELETE /v1/id/:id/ch/:ch 删除通道
5. GET /v1/id/:id/ch 罗列通道
   6）除开第4没有参数，其它1,2,3的参数为
   {
   "type":"value" // 可选"value", "GPS", "photo", "unknown"
   "name":"temperature",
   "desc":"test sensor1",
   "unit":"°C"
   }
   7)通道信息专门用一个数据库，方便刷设备下面的通道列表，采用联合主键
   id integer primary key, ch integer primary key, name text, desc text, unit text

#2014-09-13 的分格线

1. POST /v1/id/:id/ch/:ch/ts/:ts 创建数据点
2. PUT /v1/id/:id/ch/:ch/ts/:ts 编辑数据点
3. GET /v1/id/:id/ch/:ch/ts/:ts 查看数据点
4. DELETE /v1/id/:id/ch/:ch/ts/:ts 删除数据点
   5）除开第4没有参数，其它1,2,3的参数为下面，或者为更复杂的json数据类型，客户自解释
   {
   "val": 29.34
   }
   6)数据点信息专门用一个数据库，方便未来采用时间段查询，设备号查询，通道号查询
   idx integer primary key autoincrement, id integer ,ch integer, ts datetime, val text

use Promise Patterns

use Promise Design Pattern to replace the callback hell.

使用Promise设计模式来代替现在的回调。

Cache层支持

RESTful设计准则

下面RESTful准则是由HTTP,Apache的设计者Fielding大神提出的，很有参考价值：

An API is a user interface for a developer - so put some effort into making it pleasant
Use RESTful URLs and actions
Use SSL everywhere, no exceptions
An API is only as good as its documentation - so have great documentation

版本号放在URL中而非协议头中

尽量采用类似 https://www.foo.com/v1/ 结构，这样更加直观

Use query parameters for advanced filtering, sorting & searching
Provide a way to limit which fields are returned from the API
Return something useful from POST, PATCH & PUT requests
HATEOAS isn't practical just yet

尽可能使用JSON而非XML

XML有更好的可读性和结构性，但是JSON适合机器阅读，具有更好的效率和更小的空间。JSON天然的和JavaScript结合得很好，使得JSON更适合RESTful架构

You should use camelCase with JSON, but snake_case is 20% easier to read
Pretty print by default & ensure gzip is supported
Don't use response envelopes by default
Consider using JSON for POST, PUT and PATCH request bodies
Paginate using Link headers
Provide a way to autoload related resource representations
Provide a way to override the HTTP method
Provide useful response headers for rate limiting
Use token based authentication, transported over OAuth2 where delegation is needed
Include response headers that facilitate caching
Define a consumable error payload
Effectively use HTTP Status codes

use sequelize replace the sqlite3 & monogdb

修改db为mongodb

移动项目到物联网工坊

https://github.com/iot-works

Get all items!

在获取/id/时，应该返回全部结果。

push的时候最好都写一下commit message

url是不可配置的

如

    function url_sanity_check(url) {
        if(url.split('/')[2] == false){
            return false;
        }
        _.each(config["key"], function (array, index) {
            if(url.split('/')[1] === config["key"][index] ){
                return true;
            }
        });
    }

关于URL的配置应该放在iot.json中