Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAK.KO-10.0771 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2014-12-17 ÃÑÆäÀÌÁö 19
ÇѱÛÇ¥Áظí WoT¸¦ À§ÇÑ RESTful API Áöħ
¿µ¹®Ç¥Áظí RESTful API Guidelines for WoT
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØ¿¡¼­´Â À¥ ±â¹ÝÀ¸·Î ´Ù¾çÇÑ »ç¹°µéÀ» ¿¬µ¿ÇÏ´Â WoT ȯ°æ¿¡¼­ È°¿ëµÉ ¼ö ÀÖ´Â RESTful API °³¹ß¿¡ °í·ÁµÇ¾î¾ß ÇÒ »çÇ׵鿡 ´ëÇØ Á¤ÀÇÇÑ´Ù. ³·Àº »ç¾çÀÇ µð¹ÙÀ̽ºµéÀÌ ÁÖ·Î È°¿ëµÇ´Â »ç¹°À¥ ȯ°æ¿¡¼­´Â ´Ù¾çÇÑ »ç¹°µé¿¡ ´ëÇÑ Á¤º¸ ȹµæ°ú Á¦¾î µîÀ» À§ÇÑ ¹æ¹ýÀ¸·Î ±¸Á¶È­µÈ ÀÚ¿ø ¿äû°ú ÀÀ´ä ¹æ½ÄÀÎ REST ±â¹ÝÀÇ ¼­ºñ½º ¿¬°á ¹æ½ÄÀÌ Æ¯È÷ È¿°úÀûÀÏ ¼ö Àֱ⠶§¹®ÀÌ´Ù.
À̸¦ À§ÇØ º» Ç¥ÁØ¿¡¼­´Â À¥ ¾ÆÅ°ÅØóÀÇ ±âº» ±¸Á¶¿Í HTTP¸¦ ±â¹ÝÀ¸·Î ÇÏ´Â REST ¹æ½Ä¿¡ ´ëÇÑ °³¿ä¸¦ ¼³¸íÇÏ°í, È¿°úÀûÀÎ RESTful ±¸Á¶¸¦ ¸¸µé ¼ö ÀÖµµ·Ï Çϱâ À§ÇØ ÇÊ¿äÇÑ REST API ¼³°è ¿øÄ¢µéÀ» ¼Ò°³ÇÑ´Ù. REST API¸¦ ¼³°èÇϱâ À§ÇÑ ÀϹÝÀû ¼³°è ±ÔÄ¢»Ó ¾Æ´Ï¶ó, URI ½Çº°ÀÚÀÇ ¼³°è, HTTP ±â¹ÝÀÇ »óÈ£ÀÛ¿ë ¹æ¹ý, ¸ÞŸµ¥ÀÌŸ È°¿ë ¹æ¹ý, Ç¥Çö ¹æ¹ý µî¿¡ ´ëÇÑ ¼³°è ¿øÄ¢À» ¼Ò°³ÇÏ°í, REST APIÀÇ ¹®¼­È­ ¹æ¹ý¿¡ ´ëÇØ ¼³¸íÇÔÀ¸·Î½á ´Ù¾çÇÑ À¥ ÀÀ¿ë ȯ°æ¿¡¼­ Àû¿ëÇÒ ¼ö ÀÖ´Â ¿©·¯ °í·Á »çÇ×µéÀ» ÇÔ²² Á¦°øÇÏ°íÀÚ ÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à This standard introduces the design consideration of RESTful APIs for Web of Things Application. The REST architectural style is commonly applied to the design of APIs for modern web application services. A REST API consists of an assembly of interlinked resources. This set of resources is known as the REST API's resource model. In the context of the Web of Things, the RESTful model has many advantages on the low-computing power devices environment such as less overhead, less parsing complexity, statelessness, and tighter integration with HTTP.

Well-designed REST APIs can attract client developers to use the web of things services. Some of the best practices for REST API design are implicit in the HTTP standard while other pseudo-standard approaches have emerged over the past few years. The rules are to help design REST APIs with consistency in order to best serve the clients that use them.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAK.KO-10.0771.pdf TTAK.KO-10.0771.pdf            

ÀÌÀü
´ÙÀ½