Click here to close now.




















Welcome!

Microservices Expo Authors: Pat Romanski, Elizabeth White, Mike Kavis, Ian Khan, Lori MacVittie

Related Topics: Agile Computing

Agile Computing: Article

Is Web 2.0 Possible with Existing Open Source Technologies?

AJAX Pushed

If you Google "AJAX Web 2.0" you'll get over eight million hits, but what technologies will you find in that mix that can truly deliver on the promises of Web 2.0 today? While there's no single definition of Web 2.0, at its heart lays the Internet acting as a platform for social networks, where information can be created and shared in a community of interest. Rich Internet Applications (RIAs) relate to Web 2.0 concepts only in that they enhance the platform by providing a more effective user interface. AJAX relates to Web 2.0 only in that it provides a lightweight approach for developing RIAs that execute through a single ubiquitous interface, the Web browser.

An examination of the interaction models for existing social networking platforms like wikis and blogs reveals that they lack the instantaneous nature of true human interaction. This is an artifact of the synchronous Web model that must be overcome when we consider next-generation platforms envisioned in the Web 2.0 spectrum. Internet-based chat is the most basic example of the near-instantaneous interaction that Web 2.0 demands, but even delivering these basic capabilities in a scalable, lightweight, browser-based mechanism is beyond the scope of most AJAX technologies. In fact, if you sift through those eight million Google hits, you'll find only a handful of open source technologies that address the problems associated with pushing content asynchronously to the user through standard browser mechanisms. We'll provide an overview of those technologies later, but first some basics.

The Basics of Web-based Push
Industry has not standardized on a mechanism or a name for asynchronous data push to the browser. In the AJAX realm the technique goes by a variety of names including AJAX Push, Comet, and Reverse AJAX, but regardless of what you call it, the various approaches share a common characteristic. The only lightweight communication mechanism available to the browser is the HTTP protocol, but HTTP only facilitates standard request/response communication initiated from the browser to the server. To deliver responses asynchronously, it's necessary to invert the HTTP protocol by holding an open request at the server, and fulfilling that request when an update is available. The differences between standard AJAX request processing and the inverted mechanism required for push are illustrated in Figure 1.

To support asynchronous push we need to hold a browser connection open in anticipation of a server-based event that will result in presentation changes in the browser. Intuition suggests that there are issues with this approach and in this case intuition serves us well, since we face connection-related problems at both the browser and the server.

Browser Connection Limit
One of the main difficulties faced by asynchronous Web techniques is caused by the typical browser "two-connection limit." To reduce server load, the HTTP specification recommends that user agents establish at most two connections per server, but asynchronous techniques consume one of these connections as a notification channel. Considering the case where multiple browser windows are open to the same Web page, if each window attempts to establish its own connection, we quickly saturate the available connections. To work within these limitations, a single connection must be shared, but the scripting environments of distinct browser windows are isolated for security reasons, making it difficult to coordinate a shared connection. One technique that can be applied is to make use of a shared HTTP cookie, which is associated with all HTTP interaction with a given server. The cookie is shared across windows and, by manipulation through JavaScript, can be used for cross-window communication.

The problem is amplified in portal environments because legacy portal engines don't support the necessary asynchronous communication path. For push to work in multiple portlets it's not only necessary to share the browser connection, but a single shared server connection is required to marshal asynchronous responses. If portlets are deployed from multiple WARs, there's an additional complication in that the sharing mechanism must coordinate between multiple Web applications and will require some IPC mechanism to do so.

More Stories By Ted Goddard

Ted Goddard is the senior architect of the ICEfaces AJAX framework. Following a Ph.D. in mathematics, he proceeded with postdoctoral research in component and Web-based collaborative technologies. He currently participates in the JavaServer Faces and Servlet expert groups.

More Stories By Steve Maryka

Stephen Maryka is CTO at ICEsoft Technologies Inc., and leads the ICEfaces open source project. He has been involved in Java-based AJAX techniques since 2003 - a time before the term "AJAX" was even coined. Prior to joining ICEsoft, Steve was co-founder of AudeSi Technologies where he served as VP of Technology and led Java product development for Internet appliances. After AudeSi was acquired by Wind River Systems in 2000, he served as a principle technologist there until joining ICEsoft.

Comments (2) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
radixweb 08/13/08 09:21:00 AM EDT

Hey, Great Post.. Thanks for this..

MiamiWebDesigner 08/02/08 09:34:25 AM EDT

Web 2.0 Is Like Pornography

Like so many tech articles posted since Tim O'Reilly coined the term in 2004, this one references "Web 2.0" as if it were something tangible--or at least a concept with clear, concise definition. It is not. In 2006, Web founder Sir Tim Berners-Lee sagely observed that "nobody knows what it means":

http://tinyurl.com/y6ewzy

In 2007, Michael Wesch put together this video that supposedly "explains what Web 2.0 really is about":

http://tinyurl.com/6pdz2q

It is a cool video. But the message is all about XML and how it can be used to separate form and content. There was no mention of CSS and XHTML, but no matter. I was writing XML parsers in the '90s, and XHTML/CSS web design pre-dates "Web 2.0" as well. No cigar, Professor Wesch.

And now in 2008, the most honest thing we can say is that "Web 2.0" means whatever the techno-marketeer (ab)using it wants it to mean. Otherwise, why would intelligent people like Isaac O'Bannon still be writing articles asking "What is Web 2.0?":

http://tinyurl.com/5solok

And, why would McKinsey's just-released best-of-breed report entitled "Building the Web 2.0 Enterprise" ...

http://tinyurl.com/6sxls7

... include no attempt at defining the term other than to list the "Web 2.0 Tools" that comprise or enable it? And even there, the chief ingredient is identified only as "Web Services", adding more mystery to the mix as one ethereal term is offered up to explain another.

As originated in an Onstartups.com website design posting...

http://tinyurl.com/576sgs

... "Web 2.0" is like pornography: Nobody has defined it, but you know it when you see it.

Bruce Arnold, Web Designer, Miami Florida
http://www.PervasivePersuasion.com

@MicroservicesExpo Stories
SYS-CON Events announced today that the "Second Containers & Microservices Expo" will take place November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin,...
Container technology is sending shock waves through the world of cloud computing. Heralded as the 'next big thing,' containers provide software owners a consistent way to package their software and dependencies while infrastructure operators benefit from a standard way to deploy and run them. Containers present new challenges for tracking usage due to their dynamic nature. They can also be deployed to bare metal, virtual machines and various cloud platforms. How do software owners track the usag...
Our guest on the podcast this week is JP Morgenthal, Global Solutions Executive at CSC. We discuss the architecture of microservices and how to overcome the challenge of making different tools work together. We learn about the importance of hiring engineers who can compose services into an integrated system.
Alibaba, the world’s largest ecommerce provider, has pumped over a $1 billion into its subsidiary, Aliya, a cloud services provider. This is perhaps one of the biggest moments in the global Cloud Wars that signals the entry of China into the main arena. Here is why this matters. The cloud industry worldwide is being propelled into fast growth by tremendous demand for cloud computing services. Cloud, which is highly scalable and offers low investment and high computational capabilities to end us...
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
One of the ways to increase scalability of services – and applications – is to go “stateless.” The reasons for this are many, but in general by eliminating the mapping between a single client and a single app or service instance you eliminate the need for resources to manage state in the app (overhead) and improve the distributability (I can make up words if I want) of requests across a pool of instances. The latter occurs because sessions don’t need to hang out and consume resources that could ...
Microservices has the potential of significantly impacting the way in which developers create applications. It's possible to create applications using microservices faster and more efficiently than other technologies that are currently available. The problem is that many people are suspicious of microservices because of all the technology claims to do. In addition, anytime you start moving things around in an organization, it means changing the status quo and people dislike change. Even so, micr...
"We've just seen a huge influx of new partners coming into our ecosystem, and partners building unique offerings on top of our API set," explained Seth Bostock, Chief Executive Officer at IndependenceIT, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
Digital Transformation is the ultimate goal of cloud computing and related initiatives. The phrase is certainly not a precise one, and as subject to hand-waving and distortion as any high-falutin' terminology in the world of information technology. Yet it is an excellent choice of words to describe what enterprise IT—and by extension, organizations in general—should be working to achieve. Digital Transformation means: handling all the data types being found and created in the organizat...
JavaScript is primarily a client-based dynamic scripting language most commonly used within web browsers as client-side scripts to interact with the user, browser, and communicate asynchronously to servers. If you have been part of any web-based development, odds are you have worked with JavaScript in one form or another. In this article, I'll focus on the aspects of JavaScript that are relevant within the Node.js environment.
Approved this February by the Internet Engineering Task Force (IETF), HTTP/2 is the first major update to HTTP since 1999, when HTTP/1.1 was standardized. Designed with performance in mind, one of the biggest goals of HTTP/2 implementation is to decrease latency while maintaining a high-level compatibility with HTTP/1.1. Though not all testing activities will be impacted by the new protocol, it's important for testers to be aware of any changes moving forward.
This week, I joined SOASTA as Senior Vice President of Performance Analytics. Given my background in cloud computing and distributed systems operations — you may have read my blogs on CNET or GigaOm — this may surprise you, but I want to explain why this is the perfect time to take on this opportunity with this team. In fact, that’s probably the best way to break this down. To explain why I’d leave the world of infrastructure and code for the world of data and analytics, let’s explore the timing...
Learn how to solve the problem of keeping files in sync between multiple Docker containers. In his session at 16th Cloud Expo, Aaron Brongersma, Senior Infrastructure Engineer at Modulus, discussed using rsync, GlusterFS, EBS and Bit Torrent Sync. He broke down the tools that are needed to help create a seamless user experience. In the end, can we have an environment where we can easily move Docker containers, servers, and volumes without impacting our applications? He shared his results so yo...
Auto-scaling environments, micro-service architectures and globally-distributed teams are just three common examples of why organizations today need automation and interoperability more than ever. But is interoperability something we simply start doing, or does it require a reexamination of our processes? And can we really improve our processes without first making interoperability a requirement for how we choose our tools?
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
The Internet of Things. Cloud. Big Data. Real-Time Analytics. To those who do not quite understand what these phrases mean (and let’s be honest, that’s likely to be a large portion of the world), words like “IoT” and “Big Data” are just buzzwords. The truth is, the Internet of Things encompasses much more than jargon and predictions of connected devices. According to Parker Trewin, Senior Director of Content and Communications of Aria Systems, “IoT is big news because it ups the ante: Reach out ...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Our guest on the podcast this week is Adrian Cockcroft, Technology Fellow at Battery Ventures. We discuss what makes Docker and Netflix highly successful, especially through their use of well-designed IT architecture and DevOps.