이유가 뭘까?
rest 왜 쓰는 거임? 웹소켓 써야 하는거 아님?
익명(175.212)
2016-01-25 02:00
추천 0
댓글 6
다른 게시글
-
스마트포인터 많이들 쓰나여 [6]KimJa(kimchiman56) | 16.01.25추천 0
-
흔히 쓴느 NAS 같은건 라즈베리파이같은 모듈을 응용해서 만든거라 [2]돌(59.30) | 16.01.25추천 0
-
아 회사가기싫다 [1]sohotmelod..(tara4ever) | 16.01.25추천 1
-
선배님들, 코딩할때요 [4]컴공1학년(211.199) | 16.01.25추천 0
-
사이버대 컴공과 다니는거 어때요?스마트븅신(zzizilee) | 16.01.25추천 0
-
형님들 자바기초학원 어디가조은가요 [1]아배앵(39.7) | 16.01.25추천 0
-
내일 월요일이네요ㅠㅠ 좋은 밤 되세요ㅠㅠㅠㅠㅠ(27.117) | 16.01.25추천 0
-
니들 nono한테 고맙다고 애기는 하고 갤질하냐 [2]익명(175.116) | 16.01.25추천 0
-
rust 랭 아냐 니네rust(112.172) | 16.01.25추천 0
-
안녕 내 이야기좀 들어줄래 [1]으(112.172) | 16.01.25추천 0


SSL
브라우저 지원이 다 안되잖아 우리나라ie 7쓰는 할배들 아직도 많음
REST is an architectural style while WebSocket is a technology.
WebSocket is a low-level protocol, think of it as a socket on the web. Every thing, including a simple request/response design pattern, how to create/update/delete resources need, status codes etc to be build on top of it. All of these are well defined for HTTP.
WebSocket is a stateful protocol where as HTTP is a stateless protocol. WebSocket connections are know to scale vertically on a single server where as HTTP can scale horizontally. There are some proprietary solutions for WebSocket horizontal scaling, but they are not standards-based.
How will Search Engine Optimization (SEO) work with WebSocket ? Works very well for HTTP URLs. All proxy, DNS, firewalls are not yet fully aware of WebSocket traffic. They allow port 80 but might restrict traffic by snooping on it first. Security with WebSocket is all-or-nothing approach.