Matteo Spreafico (matteosp)'s Public Profile in the Diigo Community

Member since Mar 18, 2009, follows 2 people, 3 public groups, 964 public bookmarks (1006 total).

More »

Tags

Recent Tags:	clouds(0), soa(0), WebDevelopment(0), tools(0), web2.0(0), ado.net(0), MSDynamicsCRM40(0), future(0), socialmedia(0), Javascript(0), google(0), Azure(0), Frontiers(0), MultiThreading(0), threading(0), webservices(0), twitter(0), development(0), Trends(0)
Top Tags:	Movies(58), WebDevelopment(49), Ajax(44), MSDynamicsCRM(44), tools(43), soa(41), Society(37), SharePoint(35), Fun(31), SoftwareArchitecture(30)

More »

Recent Bookmarks and Annotations

Scientists create the first programmable quantum processor about 12 hours ago
HTML 5 differences from HTML 4 on 2009-11-20
- The HTML 5 draft reflects an effort, started in 2004, to study
  contemporary HTML implementations and deployed content. The draft:
  
  Defines a single language called HTML 5 which can be written in
  HTML syntax and in XML syntax.
  
  Defines detailed processing models to foster interoperable
  implementations.
  
  Improves markup for documents.
  
  Introduces markup and APIs for emerging idioms, such as Web
  applications.
- HTML 5 is defined in a way that it is backwards compatible with the
  way user agents handle deployed content.
- 3 more annotations...
- - User agents, however, will always have to support these older elements
    and attributes and this is why the specification clearly separates
    requirements for authors and user agents.
  - The HTML 5 specification will not be considered finished before
    there are at least two complete implementations of the specification. This
    is a different approach than previous versions of HTML had. The goal is to
    ensure that the specification is implementable and usable by designers and
    developers once it is finished.
  - The following areas / features defined in HTML 5 are believed to
    impact the Web architecture:
    
    The use of the DOM as a basis for defining the language.
    
    The concept of browsing contexts.
    
    The distinction between user agent requirements and authoring
    requirements.
    
    The use of imperative definitions rather than abstract definitions
    with the requirement of black-box equivalence in implementations.
    
    The new content model concepts (replacing HTML 4's block and
    inline concepts).
    
    The focus on accessibility as a built-in concept for new features
    (such as the hidden attribute, the progress
    element, et cetera) instead of an add-on (like the alt
    attribute).
    
    The focus on defining the semantics in detail (e.g. the outline
    algorithm, replacing the vague semantics in HTML 4).
    The menu and command elements.
    
    The origin concept.
    
    Offline Web application caches.
    
    The definition of the browsing context "navigation" algorithm and the
    related session history traversal algorithms.
    
    The content-type sniffing and character encoding sniffing.
    
    The very explicit definition of a parser.
    
    The contentEditable feature and the
    UndoManager feature.
    
    The Drag and Drop and Copy and Paste architecture.
    
    The cross-document messaging feature (the postMessage
    API).
    
    The new sandboxing features for iframe.
    
    The definition of URL.
Scriptlets - Quick web scripts on 2009-11-20
Web Hooks / FrontPage on 2009-11-20
- The concept of a WebHook is simple. A WebHook is an HTTP callback: an HTTP POST that occurs when something happens; a simple event-notification via HTTP POST.
- A web application implementing WebHooks will POST a message to a URL when certain things happen. When a web application enables users to register their own URLs, the users can then extend, customize, and integrate that application with their own custom extensions or even with other applications around the web. For the user, WebHooks are a way to receive valuable information when it happens, rather than continually polling for that data and receiving nothing valuable most of the time. WebHooks have enormous potential and are limited only by your imagination! (No, it can't wash the dishes. Yet.)
- 4 more annotations...
- - Push is the simplest of reasons to use WebHooks. As was just stated above, no more polling every couple of minutes to find out if there is new information. Just register a WebHook and receive the data at your doorstep as soon as it exists.
  - A Pipe happens when your WebHook not only receives real-time data, but goes on to do something new and meaningful with it, triggering actions unrelated to the original event. For example, you create a script, register its URL at a photo site, and have it email you when your mother posts a new photo.
  - Plugins: processing data and giving something in return
    
    This is where the entire web becomes a programming platform. You can use this form of WebHooks to allow others to extend your application. Facebook's Application Platform uses WebHooks in this way, and so does Google Wave's robot integration. The general idea is that a web application sending out data via WebHooks will also use the response to modify its own data. At Facebook, when you access an app, Facebook sends a WebHook out to your application saying "Hey, someone's accessing your application, what do I do?!" The application responds with, "Show the user this page..." Facebook does so, and the pattern continues in the same manner as you continue to use the application. At Google Wave, when you do something in a wave, any robot you've added as a participant is notified via a WebHook, and the robot has the ability to modify the wave in its http response. Implement WebHooks in this way in your application if you want to allow others to truly extend and enhance the abilities of your application.
  - By letting the user specify a URL for various events, the application will POST data to those URLs when the events occur. With the cheap availability of PHP hosting and even easier simple app/script hosting like AppJet or Scriptlets, handling the POST data becomes fairly trivial. How you use it is up to you and whatever you want to accomplish.
Salesforce Chatter | Collaboration Software Solutions - Collaboration Cloud - salesforce.com on 2009-11-20
Clemens Vasters, Bldg 42 : Port Bridge on 2009-11-19
- In order to increase the responsiveness and throughput for protocols that are happy to kill and reestablish connections such as HTTP does, “Port Bridge” is always multiplexing concurrent traffic that’s flowing between two parties on the same logical socket.
- With Hybrid, all connections are first established through the Service Bus Relay and then our bits do a little “NAT dance” trying to figure out whether there’s a way to connect both parties with a direct socket – if that works the connection gets upgraded to the most direct connections in-flight.
- 1 more annotations...
- - Now you might say You are using a WCF ServiceContract? Isn’t that using SOAP and doesn’t that cause ginormous overhead? No, it doesn’t. We’re using the WCF binary encoder in session mode here. That’s about as efficient as you can get it on the wire with serialized data. The per-frame SOAP overhead for net.tcp with the binary encoder in session mode is in the order of 40-50 bytes per message because of dictionary-based metadata compression. The binary encoder also isn’t doing any base64 trickery but treats binary as binary – one byte is one byte. Port Bridge is using a default frame size of 64K (which gets filled up in high-volume streaming cases due to the built-in Nagling support) and so we’re looking at an overhead of far less than 0.1%. That’s not shabby.
The power of Twitter & the “Ellen Effect” | Tannock.net on 2009-11-18
Twitter Fan Wiki - Bots, Twitter as a command-line on 2009-11-18
- Twitter can be used as a device-independent, global command line that sits on top of a large user-base. This suggests several things for the future of applications that take advantage of Twitter: for example, you could create a service that takes in commands, via Twitter, from various input devices. For a business, there is a cost-saving to be had, as well as a rapid launch and the flexibility of multiple ways of interacting with people.
» The Hierarchy Of Tweets - Analysing The Psychology of Twitter on 2009-11-18
Google Redefines Disruption: The “Less Than Free” Business Model on 2009-11-16
- In the summer of 2007, excitement regarding the criticality of map data (specifically turn-by-turn navigation data) reached a fever pitch. On July 23, 2007, TomTom, the leading portable GPS device maker, agreed to buy Tele Atlas for US$2.7 billion. Shortly thereafter, on October 1, Nokia agreed to buy NavTeq for a cool US$8.1 billion. Meanwhile Google was still evolving its strategy and no longer wanted to be limited by the terms of its two contracts. As such, they informed Tele Atlas and NavTeq that they wanted to modify their license terms to allow more liberty with respect to syndication and proliferation. NavTeq balked, and in September of 2008 Google quietly dropped NavTeq, moving to just one partner for its core mapping data. Tele Atlas eventually agreed to the term modifications, but perhaps they should have sensed something bigger at play.
- Rumors abound about just how many cars Google has on the roads building it own turn-by-turn mapping data as well as its unique “Google Streetview” database. Whatever it is, it must be huge. This October 13th, just over one year after dropping NavTeq, the other shoe dropped as well. Google disconnected from Tele Atlas and began to offer maps that were free and clear of either license. These maps are based on a combination of their own data as well as freely available data. Two weeks after this, Google announces free turn-by-turn directions for all Android phones. This couldn’t have been a great day for the deal teams that worked on the respective Tele Atlas and NavTeq acquisitions.
- 3 more annotations...
- - Google’s free navigation feature announcement dealt a crushing blow to the GPS stocks. Garmin fell 16%. TomTom fell 21%. Imagine trying to maintain high royalty rates against this strategic move by Google. Android is not only a phone OS, it’s a CE OS. If Ford or BMW want to build an in-dash Android GPS, guess what? Google will give it to them for free.
  - I then asked my friend, “so why would they ever use the Google (non open source) license version.” (EDIT: One of the commenters below pointed out that all Android is open source, and the Google apps pack, including the GPS, is licensed on top. Doesn’t change the argument, but wanted the correct data included here.) Here was the big punch line – because Google will give you ad splits on search if you use that version! That’s right; Google will pay you to use their mobile OS. I like to call this the “less than free” business model.
  - “Less than free” may not stop with the mobile phone. Google’s CEO Eric Schmidt has been quite outspoken about his support for the Google Chrome OS. And there is no reason to believe that the “less than free” business model will not be used here as well. If Sony or HP or Dell builds a netbook based on Chrome OS, they will make money on every search each user initiates. Google, eager to protect its search share and market volume, will gladly pay the ad splits. Microsoft, who was already forced to lower Windows netbook pricing to fend off Linux, will be dancing with a business model inversion of epic proportion – from “you pay me” to “I pay you.” It’s really hard to build a compensation package for your sales team on those economics.

More »

Groups

Coders

317 members, 1594 items

A group for and about coders and programming -- theory, practice, and research.
Future of the Web

90 members, 427 items

Watching the grand convergence of the desktop, the server, devices, and the Web. Topics addressed include events and emerging trends in universal interoperability, standards development, SOA, Clouds, Web-Stacks, RIA run-times, etc.
Web 2.0 Tools

695 members, 2222 items

A collection of Web 2.0 Tools and Webtop Apps for creatives, designers, musicians, filmakers, indie tv producers and digital entrepreneurs. From the MsBehaviour Files for The Big Idea, the home of New Zealand's Creative Community.