After a very busy and stressful few days, I’m ready to try to get a start on the list of post topics that have stacked up in my inbox. First is to attempt to explain the difference between Push technologies and Pull technologies and to make some suggestions on how RSS can be made to be perceived by users as a push technology as convenient as email.
Geekier purists, please note: We’re talking about PERCEIVED Push vs. PERCEIVED Pull. I’d argue that this isn’t the same thing as comparing a true push to a true pull, but that’s an argument for another day.
Web Browsing: An example of a perceived Pull Technology
The best and most common example of a pull technology is your web browser. When you type http://www.davidrothman.net into your browser’s address bar, your browser contacts the server that HOSTS my blog and asks it (preferably in a refined English accent): “Excuse me please, web server. I’d very much like to see what’s available at davidrothman.net. Could you please deliver to me the default HTML file of davidrothman.net?”
The server replies (also in the Queen’s English): “Why of course, my dear browser- please do render this HTML file for your user!”
And the web server sends the file to your browser, which your browser interprets and renders for your viewing.
What makes this a perceived pull technology? You have to direct your browser to the web page so your browser can request (or PULL) the appropriate HTML file from the server to display for you.
Email: An example of a perceived Push technology
PC Magazine’s encyclopedia defines a Push technology as “[a] data distribution technology in which selected data is automatically delivered into the user’s computer at prescribed intervals or based on some event that occurs…”
Your email is probably a good example of this. If you use a version of Microsoft Outlook at home or at work, your Outlook client (the program what is installed on your computer) checks in the email server at regular intervals (perhaps every 5 minutes or so) to see if there are new emails. If it finds there are new emails on the server for you, it downloads them to your computer for you to view.
Viva la difference!
Note that the only difference in our examples between the perceived push and the perceived pull is that the email client automatically checks for new emails at regular intervals. So when the user starts up Outlook, it automatically checks the server to see if there are new emails. If the user leaves Outlook running all day, the user will see any new emails that are received by his/her email server within 5 minutes of their arrival without the user having to tell Outlook to go check the server for new email. The web browser is seen as a perceived PULL technology because it doesn’t automatically refresh the page from the server at regular intervals (unless, of course, the web site is designed to force a refresh at regular intervals- that is done sometimes).
Is RSS a Push or a Pull?
Let’s now look at the issue raised by a member of the MEDLIB-L ListServ about RSS a few days ago:
I see RSS as a pull technology and emails as a push tech. By that, I mean, that the user has to actively seek out their RSS aggregator and read whatever it contains. Emailed TOCs, however, are pushed to their email box and they don’t have to actively seek out another program to get info. I suspect that expecting busy HC professionals to seek out anything else (such as an RSS aggregator) will decrease current awareness usage.
This is, obviously, a really valid concern. The fact of the matter is that RSS is clearly a Push technology. Why? Because once one subscribes to the feed, the aggregator checks the feed at regular intervals to see if there is new information, and automatically displays it for the user.
RSS is as much a push technology in this manner as an email client. If you keep wither client open all day, you’ll know quickly if there is a new email/post.
The real concern shown by the librarian poster to MEDLIB-L here is that her users already keep their email clients open all day, and she doesn’t want them to have to keep another client open all day for RSS feeds. That’s a totally reasonable concern. Some users might see the need to visit a web-based aggregator as an additional step to their (already hectic) day.
How to make the push of RSS more conveniently “pushy” for the user
Here are some of the ways the user can be actively notified when there are new results from their subscribed feeds without having to visit the URL of a web-based browser OR having to install a “fat client” RSS aggregator:
- If the user chooses BlogLines as her aggregator, she can install one of the many notifer tools offered by BlogLines that can, for instance, live in her Windows Taskbar and beep her when she has new information ready to be viewed via her subscribed feeds.
- There are multiple aggregators available that are plug-ins for Microsoft Outlook. If your user already uses Outlook, she may be interested in one of the following plug-ins to allow her to read RSS feeds in Outlook, too:
RSS Popper (Free)
Attensa for Outlook ($20)
BlogBot for Outlook (Free)
Please note that I have not tried these plugins myself, and cannot vouch for their quality or function. This isn’t a complete list, either; these are just the first five that I found in five minutes of searching. If any readers have used and liked an RSS plug-in for Outlook, please make a note of it in the comments for this post?
While we’re fishing for opinions among readers, are there other options you’re aware of that would help users experience RSS feeds as more of a perceived push?