Personal summary
URL unified management, unified approach to call, and must return the full URL path, can be packaged into a service, and the url is the full path (including domain name), after the changes are very convenient
Static version of the resource plus a good, unified approach to call
User passwords must be added salt, the best record in the database, each user has a different salt
Static resource version number, the version number on the line every need is not the same
For large amounts of data query, always remember to release the memory See phpexcel out of memory optimization
Phone API must specify a version number, such as / v1 / user / info, / v2 / user / info
Back-end application should record all GET, POST requests, as well as GET, POST request parameters (commercial product is very important)
Full HTTPS or CSP station operators to prevent hijacking content
Original Address: Some [personal] development should be the focus of attention
Tags: url framework CDN API importance
Intelligent Recommendation
- To create a private DNS service
- jquery event bind many times, many times the trigger, how clear history bind events
- Deceptive seven cattle CDN
- [Demo] generate two-dimensional code and bar code
- Ipv6 [blame] curl timeout
Reproduced in: https: //my.oschina.net/54php/blog/779376