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

TTAÀÇ Ç¥ÁØÇöȲ

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

Ç¥ÁعøÈ£ TTAI.OT-10.0358 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2013-12-18 ÃÑÆäÀÌÁö 0
ÇѱÛÇ¥Áظí À¥¼ÒÄÏ API
¿µ¹®Ç¥Áظí WebSocket API
Çѱ۳»¿ë¿ä¾à À¥¼ÒÄÏ(WebSocket) ÇÁ·ÎÅäÄÝÀº ¿ø°Ý È£½ºÆ®¿ÍÀÇ ¾ç¹æÇâ Åë½ÅÀ» °¡´ÉÇÏ°Ô ÇÑ´Ù À̸¦ À§ÇØ »ç¿ëµÇ´Â º¸¾È ¸ðµ¨Àº ÀϹÝÀûÀ¸·Î À¥ ºê¶ó¿ìÀú¿¡¼­ »ç¿ëµÇ´Â OBS(Origin-Based Security) º¸¾È ¸ðµ¨À» »ç¿ëÇÑ´Ù. ÀÌ ±â¼úÀÇ ¸ñÀûÀº ´Ù¼öÀÇ HTTP ¿¬°áÀ» ÇÏÁö ¾Ê°í ¼­¹ö¿Í ¾ç¹æÇâ Åë½ÅÀ» ÇÊ¿ä·Î ÇÏ´Â ºê¶ó¿ìÀú ±â¹Ý ¾ÖÇø®ÄÉÀ̼ÇÀ» À§ÇÑ ¸ÞÄ¿´ÏÁòÀ» Á¦°øÇÏ´Â °ÍÀÌ´Ù.
¿µ¹®³»¿ë¿ä¾à The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAI.OT-10.0358.pdf TTAI.OT-10.0358.pdf            

ÀÌÀü
Ä÷¯ Ȧ·Î±×·¥ÀÇ º¹¼¿ Å©±â ¹× »ö»ó ÃøÁ¤ ÀýÂ÷
´ÙÀ½
¸Ó¸®ÀåÂøÇü ¿µ»óÀåÄ¡¸¦ À§ÇÑ »ç¿ëÀÚ ½Ã¼± À̵¿ ¼Óµµ ±â¹Ý 360 ºñµð¿À ¿µ»ó Ç°Áú Á¦¾î ½ÅÈ£ ü°è