1월, 2013의 게시물 표시

Comet vs WebSocket

1. Comet a  web application  model in which a long-held  HTTP  request allows a  web server  to  push  data to a  browser , without the browser explicitly requesting it. (  http://en.wikipedia.org/wiki/Comet_(programming) ) Implementations 1) polling  2) long polling:  3) streaming : use chunked 2. WebSocket a web technology providing  full-duplex  communications channels over a single  TCP  connection (  http://en.wikipedia.org/wiki/WebSocket ) Features -  Like  TCP , WebSocket provides for  full-duplex  communication -  Websocket differs from TCP in that it enables a stream of messages instead of a stream of bytes WebSockets connection limit | Chromium | Chrome | Safari | Firefox | Opera | |      924      |    3237   |  2970  |   200    |   900    | ex) http://www....

Jetty

이미지
1. Jetty?  - HTTP server, HTTP client, and javax.servlet  container 2.  Features  - open source  - Small footprint  - Asynchronous (  http://wiki.eclipse.org/Jetty/Feature/Continuations )  - Enterprise scalable  - Embeddable (  http://wiki.eclipse.org/Jetty/Tutorial/Embedding_Jetty )  3. License  - Apache License 2.0  - Eclipse Public License 1.0 4. Owner  - <=6 codehaus   - 7 <= eclipse (  http://wiki.eclipse.org/Jetty/ ) 5. Architecture ( http://wiki.eclipse.org/Jetty/Reference/Jetty_Architecture )  - Conenctor SocketConnector  - for few busy connections or when NIO is not available BlockingChannelConnector  - for few busy connections when NIO is available( This connector uses efficient NIO buffers with a traditional b locking thread mode) SelectChannelConnector  - for many mostly idle connections or asynchronous handling of Ajax ...