The New 3-Tier Architecture:HTML5, Proxies, and APIs by Brian Mulloy and Kevin Swiber (Apigee)
Companion video here : http://goo.gl/YBECx
Via Nicolas Weil
Research and publish the best content.
Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
Already have an account: Login
nodeJS and Web APIs
68.8K views |
+1 today
 Your new post is loading...
Your new post is loading...
Scoop.it!
Here is a guide from @silviapfeiffer to Plugin-free video conferencing in the browser!
Websocket server code: http://ow.ly/b5yF7 Via Nicolas Weil 
Scoop.it!
HTML is the lowest common denominator in a world were the number of devices are steadily growing. In such a world, our API should be hypermedia driven and we should consider choosing HTML as the media type for our APIs. If we choose this, we can enhance the API with CSS and JavaScript, making the API human-friendly as well. Further, we can use Adaptive Web Design to make the best possible experience for all types of browsers and devices.
This kind of solution has some risks and technical issues related to it though. And it is not a silver bullet. Via Nicolas Weil
|
Scoop.it!
Through HTML5 and the corresponding standards, modern browsers get more standarized features with every release. Most people have heard of websockets that allows you to easily setup a two way communication channel with a server, but one of the specifications that hasn't been getting much coverage is the webrtc specificiation.
With the webrtc specification it will become easier to create pure HTML/Javascript real-time video/audio related applications where you can access a user's microphone or webcam and share this data with other peers on the internet. For instance you can create video conferencing software that doesn't require a plugin, create a baby monitor using your mobile phone or more easily facilitate webcasts. All using cross-browser features without the use of a single plugin. Via Nicolas Weil
Scoop.it!
This is the world's first open source HTML5 SIP client (May 12, 2012) entirely written in javascript for integration in social networks (FaceBook, Twitter, Google+), online games, e-commerce sites... No extension, plugin or gateway is needed. The media stack rely on WebRTC.
The client can be used to connect to any SIP or IMS network from your preferred browser to make and receive audio/video calls and instant messages.
The protocol parsers (SIP, SDP...) are highly optimized using Ragel lookup tables and is suitable for embedded systems with limited memory and low computing power. Via Nicolas Weil
|
Great work, just what I was looking for! Thanks for sharing!