Posted
23 Feb 2010 @ 15:23

Categories

Comments
2 Comments

Author
Alex

What Makes A Rich Internet Application (RIA)?

Disclaimer: This blog post may seem a little outdated, after all the term RIA seems to be slowly dropping out of the hype-o-sphere and been replaced with the “cloud”, however, rich internet applications are still the cutting edge of many an enterprise implementation, hence this blog post.


The internet is changing, connections are getting faster, web browsers are getting more advanced and the technologies behind the internet are being constantly improved & updated. Due to this rapid evolution more and more companies are offering services that run on the cloud, accessible anywhere, anytime, anyplace.

Virtually every application that an average use would expect to find on their desktop computer can now be found somewhere on the internet. These are the rich internet applications, applications that finally break free of the desktop into the word of infinite storage and always on availability. This blog post aims to discuss the factors that are required (in my opinion) to produce a rich internet application.

Definition

According to David Mendels (one of the group that coined the phrase ‘rich internet application’ at Macromedia) the most basic definition of an RIA is ‘no page refresh’ (or ‘single screen’ depending on your interpretation). But he himself admits that this was the definition ‘at the time’. [Based on a comment by David at RedMonk].

In the current web-sphere many websites appear to classify themselves as RIAs, this probably due, in part, to the rise of the term ‘rich internet application’ as a buzz-phrase among developers and technology publications. Many technologists involved with RIAs now argue that any website that requires some form of browser-based plugin can be categorised as a RIA, but in the a world of desktop-replacement web applications does the term still apply to websites that simply include a flash video or make extensive use of AJAX to prevent page reloading?

Redefining RIAs

After trawling through many of the different websites that consider themselves rich internet applications I fully agree with the original definition that an RIA must have no (or very little) page refresh, this is one of the factors that makes an RIA more like a desktop application in terms of user experience, you wouldn’t expect the application window in Excel to completely re-draw itself every time you switch work books would you, so why put up with it in web applications that you use.

Every website I came across that I would consider to be an RIA also shared another common attribute, the lack of full page scroll bars. Many of them contained scroll bars to navigate through subsections of content but none ever forced me to trawl through large pages and lose access to key navigational features. Again, this is reminiscent of most, if not all, desktop applications. A desktop application will nearly always retain placement of navigational features the most obvious of these being the menu bar at the top of a window (or screen).

The use of browser plugins and ‘rich media’ however were not present in the RIAs that I came across. Many created a more than optimal user experience through the use of JavaScript, HTML and a few images, features available in all modern web-browsers.

Personally I believe that the only websites that should be considered ‘rich internet applications’, the key word being ‘applications’ are those that most effectively simulate the desktop application user experience; this does not however mean that RIAs should only be limited to the functionality that a desktop application can provide. The World Wide Web offers far greater scope in terms of storage, processing, scalability, accessibility and social interaction, features which should be embraced in the creation of rich internet applications and can only serve to augment the user experience.

Conclusion

In this blog post I have discussed in very simplistic terms, what, in my opinion, makes a RIA. It isn’t the inclusion of media heavy content, or the ability to load content without re-loading the whole page. It is the ability of a website to simulate a desktop user experience, effectively allowing the user to easily replace any desktop application with a browser-based clone.

In the context of modern rich internet applications the browser should be seen, not as a way of ‘browsing the internet’, but as a shell that provides a user with access to the applications which they use every day. The web browser is the operating system of the RIA world.

Check back soon.

Posted
03 Oct 2006 @ 22:32

Categories

Comments
None

Author
Alex

Anti-DRM

Well, today, or at least some time around today in GMT time is Anti-DRM day. As a sideline to my normal ramblings I thought I would have a go at making my position clear. By the end of this post my position will probably be about as clear as mud due to my lack of writing skills, bit I’ll give it a go anyway.

In my general opinion DRM is a bad thing, or at least having many different forms of DRM is a bad thing. I don’t think that anyone would be so against DRM if it was compatible across devices & softwares, for example it really wouldn’t bother me as long as I could listen to Windows Media DRM’d files on my iPod and iTunes DRM’d files on Media Player.

In the original formats used to distribute media the fact that they were physical objects with, at first, no way to copy them provided some sort of built in protection. You could lend an LP to someone but if they wanted a copy they would have to go out and buy it themselves. With the advent of cassette recorders bootleg copies could be easily made, but it wasn’t necessarily the nicest way to listen to the music. CD’s at first could also be copied onto tape, then onto other CD’s but it was time consuming and expensive. The internet and MP3 (generally) has however opened up a massive way to ‘share’ files with other people. The main issue though is this word ‘share’.

If sharing were truly what was going on then it wouldn’t be so bad. You could lend someone a file but after a while it would expire, essentially giving it back, much as it was initially with LP’s, cassettes and CD’s, but when people stop buying music then income for companies decreases.

We all know that in reality artists are paid too much but if music was just given away all we would get is cheap & shoddy bands with records no one really wants.

I suppose what I am trying to say is that DRM should really be unified and refined and until this happens, get rid of it. I want to listen to my music the way I want, without restrictions.

Posted
22 Jun 2006 @ 21:46

Categories
, , ,

Comments
None

Author
Alex

Mini-ITX Testing Server [Updated]

Mini-ITX

This is my first in hopefully a long line of tech based posts about my experiences and things that I see on the internet. I thought I would write this post in the form of a story. So I’ll begin.

When I first started developing websites they were small, primarily static websites that would run quite comfortably on an Apache testing server on the computer I was also developing the website on. Unfortunately, my interests widened and large Ruby on Rails or ColdFusion websites would consume all of the computers resources preventing me from doing any developing what so ever. This led me to the decision that I needed an independent server to test websites on.

The first server that I set up was based on a Dell Optiplex GLx Pentium II. I even had to rip the CD-ROM out of it to fit a second hard drive in so that I would have enough space for the OS (Debian 3.1 Sarge) this was great until I needed to access the server remotely and run FastCGI, in the end this server slowed down to a snails pace.

I based my second attempt on a specification as I thought it would lead me to a better result. The specification I thought of was as follows;

  • Small footprint.
  • Quiet operation.
  • Low running temperature.
  • USB for backup.
  • Plenty of storage space.

After my searching’s through the internet I came across the Mini-ITX form factor and decided this would be my best option. All the components that I used were sourced from LinITX and eBay and assembled by myself. The end specification including software is;

Hardware:


  • Motherboard: VIA EPIA 5000 Eden

  • Processor: VIA Eden 533Mhz EBGA, Fanless

  • Memory: 256MB Kingston Low Profile PC133

  • Storage: Seagate ST92011A – 20GB (IDE), IBM DMCA21440 – 1.4GB (USB), 24×8×4 Slim CD-RW (IDE)

  • Case: Cubid 3688 (Black), 1x Case Fan, 12V Power Board

System Software:


  • OS: Ubuntu 6.06 LTS Server

  • Kernel: 2.6.15

  • Bootloader: Grub 0.9.7

Server Software:


  • Webserver: Apache 2.0.55

  • PHP: 5.1.2

  • Database: MySQL 5.0.12

  • CGI: FastCGI 2.4.2

  • Ruby: 1.8.4 inc. Rails 1.1.2

The server runs very quickly, very quietly and as you can see from the image above it is very small.

The aim of this post is to help anyone in the same situation as me to get a setup that works. Hope it helps.

Back soon.

Update: Something I forget to mention in the original post that I remembered when re-installing the other day is that the default kernel with the Ubuntu 6.06 Server disk does not function correctly with the VIA Eden processor. If you use this disk you must install, re-boot from CD and select repair installation, then using ‘apt-get’ or Aptitude install the kernel ‘i386 – 2.6.15’ from one of the Ubuntu repositories. When you restart everything should be working fine.