With the accelerating emergence of mobile devices HTML5 takes centre stage. While the first round of the "browser wars 2.0" was all about speed, the second round is about HTML5 compatibility behaviour. With the dominance of Android and iOS in the mobile market Microsoft's Internet Explorer isn't the gold standard for browsers anymore, the test results rather show IE as trying to catch up. Furthermore, since it isn't a standard if it doesn't allow for divergent interpretation, Microsoft implements HTML5 features different than the rest, creating a headache for developers. The irony in the whole situation is, that Microsoft won "browser wars 1.0" because the implemented HTML more faithful that its then competitors.
Quite some organisations claim (with various levels of credibility) to be stuck/standardised on IE (which I usually reply to with: "Interesting, what version of IE is running on your CEO's iPad?"), so you can't use all the new fancy stuff you could use on the mobile devices (until Windows Phone7 becomes popular and the "IE does it differently" headache starts on mobile). Luckily there is a cure: Chrome Frame. It installs inside IE and doesn't load any pages until you tell it so. So all the legacy code can still run with IE, but your new stuff uses Chrome's webkit rendering engine, solves a lot of XPages/Dojo headaches too. There are a few steps to get going:
Add <meta http-equiv="X-UA-Compatible" content="chrome=1"> to your HTML head section. This will ensure Chrome Frame is activated when rendering your page. If all of your applications on your (Domino) server should use it, you also can use a HTTP header (that's the web/Internet Sites section in the Domino directory) X-UA-Compatible: chrome=1
Long Term Storage and Retention
Thu, Aug 14th 2014 6:14a Stephan H Wissel Not just since Einstein time is relative. For a human brain anything above 3 seconds is long term. In IT this is a little more complex.
Once a work artefact is completed, it runs through a legal vetting and it either goes to medium or long term storage. I'll explain the difference in a second. This logical flow manifests itself in multiple ways in concrete implementations: Journaling (both eMail and databases), archival, backups, write-once copies. Quite often all artifacts go to medium term [read] Keywords: domino
Time stamped encrypted archives
Wed, Aug 13th 2014 9:12a Stephan H Wissel Developers use Version Control, business users Document management and consultants ZIP files.
From time to time I feel the need to safeguard a snapshot in time outside the machine I'm working with. Since "storage out of my control" isn't trustworthy, I encrypt data. This is the script I use:
# Saves the given directory (%1) in an SSL encrypted zip file (%2) within
# the personalFiles folder. The name [read] Keywords: connections
Designing a REST API for eMail
Sat, Aug 9th 2014 11:12a Stephan H Wissel Unencumbered by standards designed by committees I'm musing how a REST API would look like.
A REST API consists of 3 parts: the URI (~ URL for browser access), the verb and the payload. Since I'm looking at browser only access, the structured data payload format clearly will be JSON with the prose payload delivered in MIME format. I will worry about calendar and social data later on.
The verbs in REST are defined by the HTTP standard: , PUT, and DELETE. My base url would be http://localhost [read] Keywords: ibm
Workflow for beginners, Standards, Concepts and Confusion
Thu, Jul 24th 2014 10:12a Stephan H Wissel The nature of collaboration is the flow of information. So naturally I get asked about Workflows and its incarnation in IT systems a lot. Many of the question point to a fundamental confusion what Worflow is, and what it isn't. This entry will attempt to clarify concepts and terminology
Wikipedia sums it up nicely: "A workflow consists of an orchestrated and repeatable pattern of business activity enabled by the systematic organization of resources into processes that transform materials, pro [read] Keywords: collaboration
Warriors of Light
Sun, Jul 20th 2014 11:15a Stephan H Wissel Inspired by Paulo Coelho's manual for the Warrior of the Light:
Warriors of Light
We were born from the stars
Descended from the heavens
Armed with compassion
Determined to end the suffering
Subjected to the human condition
Battling ignorance with wisdom
Laying our lives for the liberation from illusion
When you look in the mirror - remember!
You are one of us. [read] Keywords:
Sun, Jul 13th 2014 1:12p Stephan H Wissel I like to cycle, I do that often and from time to time I have fun with traffic participants. One of the interesting challenges are multi-lane crossings (note to my overseas readers: Singapore follows the British system of driving on the left, so cyclists are supposed to cycle on the left edge of the road - which makes me edgy in some situations. So for right driving countries, just flip the pictures) where the outer lane allows more than one direction. Like these:
Road rules do require the [read] Keywords: google
From XML to JSON and back
Fri, Jul 11th 2014 8:12p Stephan H Wissel In the beginning there was csv and the world of application neutral (almost) human readable data formats was good. Then unrest grew and the demand for more structure and contextual information grew. This gave birth to SGML (1986), adopted only by a few initiated.
Only more than a decade later (1998) SGML's offspring XML took centre stage. With broad support for schemas, transformation and tooling the de facto standard for application neutral (almost) human readable data formats was established [read] Keywords: application
The folly of root cause analysis
Wed, Jul 9th 2014 6:12a Stephan H Wissel IT support's dealing with management is a funny business. Whenever something goes wrong, support teams engage in "defensive blaming" and the elusive quest for a root cause.
I've seen this quest (and blaming god and country along the way if it doesn't appear) taking priority over problem resolution and prevention. The twisted thought is: "If I'm not sure about the (single) root cause, I can't neither fix nor prevent it from happening again".
Why is that a folly?
It paralyses: If a pe [read] Keywords: application