. y i i f r a m e w o r k . c o m / d o c / g u i d e Q i a n g X u e, A l ex a n d er M a k a r o v , C a r s t en B r a n d t , K l i m o v P a u l , a n d m a n y co n t r i b u t o r s f r o m t h t u t o r i a l i s r e l e a s e d u n d e r t h e T e r m s o f Y i i D o c u m e n t a t i o n . C o p y r i g h t 2 0 1 4 Y i i S o f t w a r e L L C . A l l R i g h t s R e s e r v e d . C o n t h a t i s Y i i . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 . 2 U p g r a d i n g f r o m V e r s i o n 1 . 1 . . . . . . . . . . . . . . . . . . . 2 2 G e t t i n g S t a r t e d 1 3

fi n i t i v e G u i d e t o Yi i . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. 2 Ne w F e at u r e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. 2. 1 Ve r s s i on 1. 0. 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. 3 Up gr ad i n g f r om Ve r s i on 1. 0 t o 1. 1 . . . . . . . . . . . . . . . . . . . . . . . 3 1. 3. 1 C h an ge s os . . . . . . . . . . . . . . . . . 3 1. 3. 2 C h an ge s R e l at e d w i t h E age r Load i n g f or R e l at i on al Ac t i v e R e c or d . 4 1. 3. 3 C h an ge s R e l at e d w i t h T ab l e Al

fi n i t i v e G u i d e t o Yi i . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. 2 Ne w F e at u r e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. 2. 1 Ve r s . . . 3 1. 3. 2 W h at i s Yi i B e s t f or ? . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. 3. 3 How i s Yi i C om p ar e d w i t h O t h e r F r am e w or k s ? . . . . . . . . . . . . r e m e n t s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. 5 C r e at i n g F i r s t Yi i Ap p l i c at i on . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. 5. 1 C on

a k a r o v , C a r s t en B r a n d t , K l i m o v P a u l , a n d m a n y co n t r i b u t o r s f r o m t h e Y i i co m m u n i t y 简体中文 t r a n s l a t i o n p r o v i d ed b y : h t t p s : / / y u , s h i - y a n g , i y u a n c, x i a o l i u s h i f u , j h q 0 1 1 3 , f u n s o n 8 6 , r i v er l et , a b r a h a m g r ey s o n , f en g y h 轔 轨 轩 轳 轴 轵 轴 软 轲 轩 轡 转 轩 轳 轲 轥 转 轥 轡 轳 轥 轤 轵 轮 轩 轩 的开发作出贡献。 轙 轩 轩 开发者团队始终对 轗 轥 轢 开发趋势和其他框架及项目中的最佳实践和特性保持密切关注， 那些 1 h t t p s : / / w w w . y i i f r a m e w o r k . c o m / t e a m 輱 輲 轃 轈 轁 轐 轔 轅 轒 輱 輮 介绍（轉 轎 轔 轒 轏 轄 轕 轃 轔 轉 轏 轎 ） 有意义的最佳实践及特性会被不定期的整合进核心框架中，

to our wiki under Who’s Using Falcon? [https://github.com/falconry/falcon/wiki/Who's-using-Falcon%3F] You might also like to view our Add-on Catalog [https://github.com/falconry/falcon/wiki/Add- on-Catalog] while /players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements └──────┘ └────────────────────────────────┘ Action Resource Identifier In the REST architectural style, the URL only identifies the resource; it does not

to our wiki under Who’s Using Falcon? [https://github.com/falconry/falcon/wiki/Who's-using-Falcon%3F] You might also like to view our Add-on Catalog [https://github.com/falconry/falcon/wiki/Add- on-Catalog] while /players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements └──────┘ └────────────────────────────────┘ Action Resource Identifier In the REST architectural style, the URL only identifies the resource; it does not

to our wiki under Who’s Using Falcon? [https://github.com/falconry/falcon/wiki/Who's-using-Falcon%3F] You might also like to view our Add-on Catalog [https://github.com/falconry/falcon/wiki/Add- on-Catalog] while /players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements └──────┘ └────────────────────────────────┘ Action Resource Identifier In the REST architectural style, the URL only identifies the resource; it does not

to our wiki under Who’s Using Falcon? [https://github.com/falconry/falcon/wiki/Who's-using-Falcon%3F] You might also like to view our Add-on Catalog [https://github.com/falconry/falcon/wiki/Add- on-Catalog] while /players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements └──────┘ └────────────────────────────────┘ Action Resource Identifier In the REST architectural style, the URL only identifies the resource; it does not

/players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements falcon class Resource: def on_get(self, req, resp): doc = { 'images': [ { 'href': '/images/1eaf6ef1-7f2d-4ecc-a8d5-6e8adba7cc0e.png' } ] } # Create a JSON representation of the resource resp.text = json msgpack class Resource: def on_get(self, req, resp): doc = { 'images': [ { 'href': '/images/1eaf6ef1-7f2d-4ecc-a8d5-6e8adba7cc0e.png' } ] } resp.data = msgpack.packb(doc, use_bin_type=True) resp.content_type

/players/45301f54 might identify the “individual player with ID 45301f54”, and /players/45301f54/achievements the “list of all achievements for the player resource with ID 45301f54”. POST /players/45301f54/achievements falcon class Resource: def on_get(self, req, resp): doc = { 'images': [ { 'href': '/images/1eaf6ef1-7f2d-4ecc-a8d5-6e8adba7cc0e.png' } ] } # Create a JSON representation of the resource resp.text = json msgpack class Resource: def on_get(self, req, resp): doc = { 'images': [ { 'href': '/images/1eaf6ef1-7f2d-4ecc-a8d5-6e8adba7cc0e.png' } ] } resp.data = msgpack.packb(doc, use_bin_type=True) resp.content_type