Nodefest2011-Live
•
4 likes•1,201 views
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
Report
Share
Report
Share
Download to read offline
Recommended
Test it in Node.js
About Testing for Node.js
@2010/3/24
Blog: http://d.hatena.ne.jp/Jxck/20110328/1311171999
UST: http://www.ustream.tv/recorded/13530917
Http2 on go1.6rc2
This document discusses HTTP/2 support in Go 1.6. It notes that the net/http package now supports HTTP/2 out of the box. It provides code samples showing how a server can be configured with and without HTTP/2 support. It also describes how HTTP/2 functionality like HPACK header compression, server push, flow control, and priority are implemented in Go net/http. Finally, it summarizes the current level of HTTP/2 specification compliance and areas still in development.
ORTC SVC SimulCast
This document discusses ORTC SimulCast and how it differs from WebRTC 1.0. It explains that ORTC is WebRTC 1.0 plus SimulCast and multi-stream interoperability. It then defines SimulCast and describes AVC and SVC SimulCast approaches. It provides details on SVC including base layers, enhancement layers, parameters like temporal, spatial and quality layers. The document also outlines the changes in the ORTC API compared to the previous PeerConnection API and provides an overview of the new classes-based architecture. It notes that WebRTC NV will merge aspects of ORTC and ends by providing additional resources.
Isomorphic Architecture & Interface
isomorphic interface for front + proxy + back layer.
at #isomorphic_meetup
Extensible web #html5j
This document discusses how exposing low-level capabilities of the web platform can allow developers to extend it forward. It argues that technologies like ServiceWorker, Fetch, Cache, and others provide low-level APIs that explain existing features like HTML and CSS. This allows authors to understand and replicate them. It provides examples of how these low-level APIs can be used for offline applications and beyond. The document advocates wrapping these APIs in new libraries and frameworks to build the next generation of the web.
Extensible web
This document discusses extending the capabilities of the web by exposing low-level application programming interfaces (APIs). It argues that browser vendors should lead this effort by first implementing proof-of-concepts based on low-level APIs, then creating specifications based on feedback. This would allow web developers to build on these foundations and extend the web in new ways. As an example, the document discusses how the author implemented the Fetch API across Node.js and browsers to allow truly isomorphic code. It presents a vision of compounding these efforts to eventually implement higher-level APIs like XMLHttpRequest on top of lower-level APIs, extending the capabilities of the web platform.
Recommended
Test it in Node.js
About Testing for Node.js
@2010/3/24
Blog: http://d.hatena.ne.jp/Jxck/20110328/1311171999
UST: http://www.ustream.tv/recorded/13530917
Http2 on go1.6rc2
This document discusses HTTP/2 support in Go 1.6. It notes that the net/http package now supports HTTP/2 out of the box. It provides code samples showing how a server can be configured with and without HTTP/2 support. It also describes how HTTP/2 functionality like HPACK header compression, server push, flow control, and priority are implemented in Go net/http. Finally, it summarizes the current level of HTTP/2 specification compliance and areas still in development.
ORTC SVC SimulCast
This document discusses ORTC SimulCast and how it differs from WebRTC 1.0. It explains that ORTC is WebRTC 1.0 plus SimulCast and multi-stream interoperability. It then defines SimulCast and describes AVC and SVC SimulCast approaches. It provides details on SVC including base layers, enhancement layers, parameters like temporal, spatial and quality layers. The document also outlines the changes in the ORTC API compared to the previous PeerConnection API and provides an overview of the new classes-based architecture. It notes that WebRTC NV will merge aspects of ORTC and ends by providing additional resources.
Isomorphic Architecture & Interface
isomorphic interface for front + proxy + back layer.
at #isomorphic_meetup
Extensible web #html5j
This document discusses how exposing low-level capabilities of the web platform can allow developers to extend it forward. It argues that technologies like ServiceWorker, Fetch, Cache, and others provide low-level APIs that explain existing features like HTML and CSS. This allows authors to understand and replicate them. It provides examples of how these low-level APIs can be used for offline applications and beyond. The document advocates wrapping these APIs in new libraries and frameworks to build the next generation of the web.
Extensible web
This document discusses extending the capabilities of the web by exposing low-level application programming interfaces (APIs). It argues that browser vendors should lead this effort by first implementing proof-of-concepts based on low-level APIs, then creating specifications based on feedback. This would allow web developers to build on these foundations and extend the web in new ways. As an example, the document discusses how the author implemented the Fetch API across Node.js and browsers to allow truly isomorphic code. It presents a vision of compounding these efforts to eventually implement higher-level APIs like XMLHttpRequest on top of lower-level APIs, extending the capabilities of the web platform.
HTTP2Study chronicle #http2conf
This document summarizes the local activities in Japan related to HTTP/2, including meetups organized by the HTTP2Study group to discuss the HTTP/2 specification and implementations. The group also organizes hackathons and issues discussions. Resources produced by the group include test cases for the HPACK header compression format and a work-in-progress test case for HTTP/2 frames. The group maintains a wiki documenting implementations in Japan and guides for building simple HTTP/2 clients and servers. Upcoming activities include meetups at HPBN and IETF 91 to discuss HTTP/2.
Updates of socket.io@1.0
Socket.IO version 1.0 was released in June 2014 after 3 years of development. The new version includes improvements like Engine.IO for better performance, an upgraded mechanism, binary support, client libraries hosted on CDNs, better connection handling, debugging tools, and an improved API. It also addresses issues like intermediaries and delays in the handshake process between the client and server. The developer announced plans for Japanese documentation and more meetups around Socket.IO in Japan.
Why HTML Form dose not support PUT & DELETE ?
The document discusses why HTML forms have traditionally only supported GET and POST methods, not PUT and DELETE. It provides historical context, from the origins of HTTP/1.0 and HTML 4.0 through proposals in XForms and the current discussions in HTML5. While forms were originally designed for GET/POST submission before Ajax existed, recent draft extensions aim to enhance HTTP request generation from forms to support the full HTTP/1.1 method set through new attributes.
Next generation web talk @cross2014
Slide at Next generation web talk at http://www.cross-party.com/programs/next/
HTTP2 & HPACK #pyfes 2013-11-30
introduction to HTTP2 & HPACK
based on
http2 draft-08
hpack draft-04
at pyfes 2013.11 http://connpass.com/event/4273/
Network server in go #gocon 2013-11-14
The document discusses network programming and I/O in Go. It begins with an introduction to the speaker and then discusses building TCP servers and clients in Go using packages like net, bytes, encoding/binary, and bufio. It provides code examples of handling connections and reading/writing bytes slices. It also discusses building an HTTP/2 server in Go using goroutines, binary framing, and cryptography libraries.
SPDY & HTTP2.0 & QUIC - #bpstudy 2013-08-28
SPDY HTTP2 and QUIC are protocols for improving web performance. SPDY was developed by Google and provided features like request multiplexing and header compression. HTTP/2 was standardized by the IETF building upon SPDY. QUIC develops reliable transport on UDP to address TCP limitations with SPDY. Current implementations include nghttp2 library and HTTP2Cat tool for testing and development.
Http2.0 Guide 2013-08-14 #http2study
This document provides a summary of the history and status of HTTP/2.0. It discusses the origins and versions of SPDY, which served as the basis for HTTP/2.0. Key aspects of HTTP/2.0 covered include multiplexing, binary frames, header compression, server push, and implementations. Tools for developing and testing HTTP/2.0 applications are also mentioned.
Next generation web talk @cross2013
Slide for
http://www.cross-party.com/programs/?p=138
movie(ja)
http://www.ustream.tv/recorded/28598269
http://www.ustream.tv/recorded/28599028
Real Time App with Node.js
This document outlines the configuration and implementation of an Express web application server with Socket.IO for real-time functionality. It describes setting up the Express server and routing, templates, and user data. It also covers adding Socket.IO support to enable real-time messaging between clients that is pushed from the server.
I visited JSConf + NodeConf + Joyent
I visited JSConf, NodeConf, Joyent.
Talk about this at CCC conference at 2011/5/24
More Related Content
More from Jxck Jxck
HTTP2Study chronicle #http2conf
This document summarizes the local activities in Japan related to HTTP/2, including meetups organized by the HTTP2Study group to discuss the HTTP/2 specification and implementations. The group also organizes hackathons and issues discussions. Resources produced by the group include test cases for the HPACK header compression format and a work-in-progress test case for HTTP/2 frames. The group maintains a wiki documenting implementations in Japan and guides for building simple HTTP/2 clients and servers. Upcoming activities include meetups at HPBN and IETF 91 to discuss HTTP/2.
Updates of socket.io@1.0
Socket.IO version 1.0 was released in June 2014 after 3 years of development. The new version includes improvements like Engine.IO for better performance, an upgraded mechanism, binary support, client libraries hosted on CDNs, better connection handling, debugging tools, and an improved API. It also addresses issues like intermediaries and delays in the handshake process between the client and server. The developer announced plans for Japanese documentation and more meetups around Socket.IO in Japan.
Why HTML Form dose not support PUT & DELETE ?
The document discusses why HTML forms have traditionally only supported GET and POST methods, not PUT and DELETE. It provides historical context, from the origins of HTTP/1.0 and HTML 4.0 through proposals in XForms and the current discussions in HTML5. While forms were originally designed for GET/POST submission before Ajax existed, recent draft extensions aim to enhance HTTP request generation from forms to support the full HTTP/1.1 method set through new attributes.
Next generation web talk @cross2014
Slide at Next generation web talk at http://www.cross-party.com/programs/next/
HTTP2 & HPACK #pyfes 2013-11-30
introduction to HTTP2 & HPACK
based on
http2 draft-08
hpack draft-04
at pyfes 2013.11 http://connpass.com/event/4273/
Network server in go #gocon 2013-11-14
The document discusses network programming and I/O in Go. It begins with an introduction to the speaker and then discusses building TCP servers and clients in Go using packages like net, bytes, encoding/binary, and bufio. It provides code examples of handling connections and reading/writing bytes slices. It also discusses building an HTTP/2 server in Go using goroutines, binary framing, and cryptography libraries.
SPDY & HTTP2.0 & QUIC - #bpstudy 2013-08-28
SPDY HTTP2 and QUIC are protocols for improving web performance. SPDY was developed by Google and provided features like request multiplexing and header compression. HTTP/2 was standardized by the IETF building upon SPDY. QUIC develops reliable transport on UDP to address TCP limitations with SPDY. Current implementations include nghttp2 library and HTTP2Cat tool for testing and development.
Http2.0 Guide 2013-08-14 #http2study
This document provides a summary of the history and status of HTTP/2.0. It discusses the origins and versions of SPDY, which served as the basis for HTTP/2.0. Key aspects of HTTP/2.0 covered include multiplexing, binary frames, header compression, server push, and implementations. Tools for developing and testing HTTP/2.0 applications are also mentioned.
Next generation web talk @cross2013
Slide for
http://www.cross-party.com/programs/?p=138
movie(ja)
http://www.ustream.tv/recorded/28598269
http://www.ustream.tv/recorded/28599028
Real Time App with Node.js
This document outlines the configuration and implementation of an Express web application server with Socket.IO for real-time functionality. It describes setting up the Express server and routing, templates, and user data. It also covers adding Socket.IO support to enable real-time messaging between clients that is pushed from the server.
I visited JSConf + NodeConf + Joyent
I visited JSConf, NodeConf, Joyent.
Talk about this at CCC conference at 2011/5/24