Group items matching

in title, tags, annotations or url

Dion Hinchcliffe has an excellent article casting Google Wave as an Enterprise game-changer. He walks through Wave first, and then through some important enterprise features: ".....to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community: Google Wave has three layers: the product, the platform, and the protocol: The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It's an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave). Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves. The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the "live" concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone's Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.

A new IETF working group has been proposed in the Real-time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg at ietf.org) by January 20, 2010. ... According to reports from developers of Internet audio applications and operators of Internet audio services, there are no standardized, high-quality audio codecs that meet all of the following three conditions: 1. Are optimized for use in interactive Internet applications. 2. Are published by a recognized standards development organization (SDO) and therefore subject to clear change control. 3. Can be widely implemented and easily distributed among application developers, service operators, and end users. ... The goal of this working group is to develop a single high-quality audio codec that is optimized for use over the Internet and that can be widely implemented and easily distributed among application developers, service operators, and end users. Core technical considerations include, but are not necessarily limited to, the following: 1. Designing for use in interactive applications (examples include, but are not limited to, point-to-point voice calls, multi-party voice conferencing, telepresence, teleoperation, in-game voice chat, and live music performance) 2. Addressing the real transport conditions of the Internet as identified and prioritized by the working group 3. Ensuring interoperability with the Real-time Transport Protocol (RTP), including secure transport via SRTP 4. Ensuring interoperability with Internet signaling technologies such as Session Initiation Protocol (SIP), Session Description Protocol (SDP), and Extensible Messaging and Presence Protocol (XMPP); however, the result should not depend on the details of any particular signaling technology.

Web application development is a long process as it involves creating a user-friendly app from scratch and one that is capable of simultaneously maintaining high performance and web security. For all developers, web application security is one area that functions partially beyond the creator's control as it is just not possible to even guess who is on the other end of the HTTP connection.

In today's world the internet travels. Not just through laptops and wireless signal, but through a growing number of smart phones. The trick? Getting your site to travel just as well. Build to Touch:  The iPhone did two things differently. The full browser was a good first, but the second changed the fundamentals of interaction in a new direction. The phone is driven by touch. The best applications and websites have navigations that compliment this. Buttons are larger and more accommodating, and interfaces become more intuitive when they seem tactile. The iPhone did two things differently. The full browser was a good first, but the second changed the fundamentals of interaction in a new direction. The phone is driven by touch. The best applications and websites have navigations that compliment this. Buttons are larger and more accommodating, and interfaces become more intuitive when they seem tactile. For the average web designer, you'll save yourself a significant amount of time and headache by simply giving the site some iPhone sensitive browser design. Applications must be approved before going live, and can require extensive knowledge of development tools.

Incredible.  Despite the title.  It's the platform stupid! excerpt: Much is being written about Gmail, Google's new free webmail system. There's something deeper to learn about Google from this product than the initial reaction to the product features, however. Ignore for a moment the observations about Google leapfrogging their competitors with more user value and a new feature or two. Or Google diversifying away from search into other applications; they've been doing that for a while. Or the privacy red herring. No, the story is about seemingly incremental features that are actually massively expensive for others to match, and the platform that Google is building which makes it cheaper and easier for them to develop and run web-scale applications than anyone else. I've written before about Google's snippet service, which required that they store the entire web in RAM. All so they could generate a slightly better page excerpt than other search engines. Google has taken the last 10 years of systems software research out of university labs, and built their own proprietary, production quality system. What is this platform that Google is building? It's a distributed computing platform that can manage web-scale datasets on 100,000 node server clusters. It includes a petabyte, distributed, fault tolerant filesystem, distributed RPC code, probably network shared memory and process migration. And a datacenter management system which lets a handful of ops engineers effectively run 100,000 servers. Any of these projects could be the sole focus of a startup.

I posted two lengthy comments here.  Can't see the forest for all the trees is the idiom that comes to mind. excerpt: With Silverlight, Microsoft continues to make it clear that they intend to use this web application framework, which they developed, to power much of what they are doing on the web going forward. Again, the problem here is that not only does Microsoft control this, but it requires a plug-in to use. Sure, they've made the plug-in available to most browsers, including the ones by rivals Google and Apple, but it's still a plug-in. It's something that's going to stop everyone from seeing the same web no matter which browser they use. This has of course long been an issue with Microsoft. Despite a clear shift within the rest of the industry toward web standards, Microsoft long played difficult with its Internet Explorer browser. They could afford to, and maybe you could even argue that it was in their interest to, because they were so dominant. It was only when a standards-based browser, Mozilla's Firefox, started biting off significant chunks of IE's market share that Microsoft shifted their position to play more nicely with standards.

Some good questions are being asked about the future of Google Wave and collaborative computing.  He misses however another important play for Wave; moving to the center of the emerging Open Web Productivity Environment. excerpt:  Google Wave is another grab for the Holy Grail of collaborative computing. But, will it be more successful than previous attempts? Whenever you see something compared to Lotus Notes, as Google Wave has been, you know to expect an uphill slog. Add a comparison to Microsoft Groove, which I have not seen but seems reasonable, and you can expect deep trouble. Both Notes and Groove are wonderful, innovative applications that have never caught on as I had hoped. Why? They are too difficult to use and develop for. They were way ahead of their time. Maybe Google Wave, a workplace collaboration application that is being rolled out to an additional 100,000 beta testers, has arrived at the right time, finding the right mix of power vs. ease-of-use, and the right metaphor for delivering it. We have an excellent story that offers "Five Reasons To Dive Into Google Wave." That is, if you can find a way to get into the beta. The big question: Can Google Wave succeed where seemingly every collaboration application that has gone has failed?

Excellent List:  Check out these 101 small business web applications - software in the cloud. The selections reflect the breadth of innovative ideas and new business pursuits at play in the small business technology cloud landscape. From sales to legal to productivity tools, we can attest that the small business technology is alive, kicking and doing extremely well in 2011. It's getting much easier and cheaper to operate a business than ever before. Absolutely great news for small business! Here is the list of categories we will cover on this post: Business Development Email Marketing Event Marketing Video Marketing Social Media Marketing Online Sales Online Payment Presentation Billing and Accounting Funding Hiring and Team Building File Sharing Legal Building Websites Website Testing Market Research CRM Productivity Customer Service Team Management Voice Communication Online Education

Eucalyptus, an open-source platform that implements "infrastructure as a service" (IaaS) style cloud computing, aims to take open source front and center in the cloud-computing craze. The project, founded by academics at the University of California at Santa Barbara, is now a Benchmark-funded company with an ambitious goal: become the universal cloud platform that everyone from Amazon to Microsoft to Red Hat to VMware ties into. [Eucalyptus] is architected to be compatible with such a wide variety of commonly installed data center technologies, [and hence] provides an easy and low-risk way of building private (i.e. on-premise or internal) clouds...Thus data center operators choosing Eucalyptus are assured of compatibility with the emerging application development and operational cloud ecosystem while attaining the security and IT investment amortization levels they desire without the "fear" of being locked into a single public cloud platform.

The World Wide Web Consortium's return to HTML standardization after years of absence has produced tensions with the more informal Web Hypertext Application Working Group (WHATWG) that shouldered the HTML burden during that absence. Some examples of language that's cropped up this month on the W3C's HTML Working Group mailing list: "childish," "intolerable," "ridiculous," "shenanigans." And there's a concrete manifestation of the divisiveness: The WHATWG and W3C versions of the HTML5 specification, though both stemming from the same source material, have diverged in some areas. Some of the differences are relatively minor, and there are strong incentives to converge the two drafts of the HTML5 specification so that browser makers and Web developers aren't faced with the prospect of incompatibilities. In the meantime, though, the overseers of the Web are clashing during a time when their important new standard is just arriving in the spotlight.

Michael Mace provides the best analysis and insight yet concerning Windows 8 and what it means to Microsoft, Windows, and Future of the Web.  Not sure i agree with the MSOffice future, but this is excellent thinking.  Glad i stumbled on Micheal Mace! excerpt: I've got to say, this is the first time in years that I've been deeply intrigued by something Microsoft announced.  Not just because it looks cool (it does), but because I think it shows clever business strategy on Microsoft's part.  And I can't even remember the last time I used the phrase "clever business strategy" and Microsoft in the same sentence. The announcement also has immense implications for the rest of the industry.  Whether or not Windows 8 is a financial success for Microsoft, we've now crossed a critical threshold. The old Windows of mice and icons is officially obsolete. That resets the playing field for everybody in computing. The slow death of Windows When Netscape first made the web important in personal computing, Microsoft responded by rapidly evolving Internet Explorer.  That response was broadly viewed as successful, but in retrospect maybe it was too successful for Microsoft's good.  It let the company go back to harvesting money from its Windows + Office monopoly, feeling pretty secure from potential challengers. Meanwhile, the focus of application innovation slipped away from Windows, toward web apps.  New software was developed first on the Internet, rather than on Windows.  Over time, Windows became more and more a legacy thing we kept because we needed backward compatibility, rather than a part of the next generation of computing. Windows was our past, the web was our future

Although there are many open source CMSes available, we're going to focus on those that are based upon PHP. The following CMSes are thus PHP-based, and use a MySQL database. The advantages of using such a CMS include portability, support and a large developer base with frequent updates and improvements. We will discuss the following four CMSes: Drupal - a free open source content management system written in PHP and distributed under the GNU General Public License Joomla - an open source content management system platform for publishing content as a Model-view-controller (MVC) web application framework PHPNuke - a web-based automated news publishing and content management system based on PHP and MySQL Wordpress - an open source CMS, often used as a blog publishing application, and is the most popular blog software in use today

Excellent guidelines for developing crossplatform smartphone apps in HTML5-CSS-JavaScript.  Covers Appcellerator, Sencha, jQuery, and Drupal.  Great resource!

Nice article from Scott M. Fulton describing Microsoft's iron fisted lock on government desktop productivity systems and the great transition to a Cloud Productivity Platform.  Keep in mind that in 2005, Massachusetts tried to do the same thing with their SOA effort.  Then Governor Romney put over $1 M into a beta test that produced the now infamous 300 page report written by Sam Hiser.  The details of this test resulted in the even more infamous da Vinci ODF plug-in for Microsoft Office desktops.   The lessons of Massachusetts are simple enough; it's not the formats or office suite applications.  It's the business process!  Conversion of documents not only breaks the document.  It also breaks the embedded "business process". The mystery here is that Microsoft owns the client side of client/server computing.  Compound documents, loaded with intertwined OLE, ODBC, ActiveX, and other embedded protocols and interface dependencies connecting data sources with work flow, are the fuel of these client/server business productivity systems.  Break a compound document and you break the business process.   Even though Massachusetts workers were wonderfully enthusiastic and supportive of an SOA based infrastructure that would include Linux servers and desktops as well as OSS productivity applications, at the end of the day it's all about getting the work done.  Breaking the business process turned out to be a show stopper. Cloud Computing changes all that.  The reason is that the Cloud is rapidly replacing client/server as the target architecture for new productivity developments; including data centers and transaction processing systems.  There are many reasons for the great transition, but IMHO the most important is that the Web combines communications with content, data, and collaborative computing.   Anyone who ever worked with the Microsoft desktop productivity environment knows that the desktop sucks as a communication device.  There was

Not surprisingly, Microsoft is going to pound on "productivity" as the key differential between their desktop-cloud-mobile computing products, and those of mobile-productivity platform challengers, Apple and Google. There are three platform contenders, and this article points out that it is Google Apps that is keeping Apple in the business productivity game. Very interesting insight. Especially since a recent Forrester Report has the Apple platform capturing 65% of all mobile business application development. And Microsoft with only 1%. Google weighs in with 13%. This is a stunning setback for Microsoft. The MS monopolist empire is built on business productivity, with 98% of clinet/server marketshare. excerpt: "Over time, Microsoft has tried to tilt the marketing message to position Surface as a "productivity tablet". Now that Surface 2 is out, the "productivity tablet" message is coming across loud and clear. But can what people use tablets at work for actually be described as "productive"? Surface might be new, but the idea of using tablets in business is not. Although Microsoft would like us to believe that a tablet that doesn't run Office and doesn't have a good solution for a keyboard can't be used in business, the iPad has been used in business since its release in April 2010. Mobile device management (MDM) allows enterprises to control which apps are available on both on BYOD and enterprise-supplied tablets. Some MDM vendors publish reports and surveys on what their customers' allow and disallow. This information can provide some insight into what apps people are typically using. Back in June, my ZDNet colleague Adrian Kingsley-Hughes reported on a report put out by one such vendor. Fiberlink gave this list of iOS apps that are commonly whitelisted: iBooks Adobe Reader Google Citrix Receiver Numbers Dropbox Pages iTunes U Keynote WebEx Along with those apps, you also need to add that apps that come with the device - namely web browsing, email,

Speaking at Gov 2.0 Expo this week, Kemp said it takes one to two minutes to launch a virtual server on Nebula. That compares to as long as nine months to order and install a server using standard processes. At Gov 2.0 Expo, Kemp demonstrated a forthcoming Web application, developed in partnership with Microsoft and called Worldwide Telescope, that will make high-res imagery of Mars available to the public. Worldwide Telescope will be hosted on Nebula. Cureton said that NASA is assessing its cloud computing strategy in parallel with an analysis of its data center requirements. In February, Federal CIO Vivek Kundra announced a government-wide data center consolidation initiative. In response to that, NASA is taking an inventory if its data center resources as a first step toward consolidation. The advantages of cloud computing are "compelling," Cureton said during a Web 2.0 Expo keynote presentation. She outlined five primary advantages of the cloud model: ....... reduced IT costs, ....... faster deployment of IT resources, ....... organizational flexibility, ....... computing resource efficiency, and ....... the ability to provide high-quality services to users and departments.