Archive for May, 2009

in the aftermath..

May 24, 2009
  1. Blood on our hands, but this too shall pass
  2. The Man Who Destroyed Eelam
Advertisements

Beauty is..

May 23, 2009

ot_home

Don’t Dream, Its Over!

May 19, 2009

Yes, project Elam died a terrible death last night.

Exhilarating happiness I feel today, couldn’t find words to express. And then I found this.
Thank you, Mr President – you showed us what we are capable of. Hail mother Lanka!

අපටද රජෙකු ඉන්නෙ.. (we too have a king)

May 17, 2009

Pictures speak a thousand words. This one certainly does.
arantalawa_massacre

That was then.
And since, we’ve defeated terrorism without the support of a coalition. And without invading someone else’s country. And did they really think we will starve without their money?

The US government and everyone who supported them should be ashamed for what they did to us. You cannot set fire to the rest of the world and think you’ll be safe in there. How they weep when they are touched for a moment, go behind and destroy shadow of it, yet ignore us when it happened to us for generations. How they are so indifferent to us, it beats us. Just remember.. like its written in the stones, that ‘Those Who Cannot Remember the Past Will Be Condemned to Repeat It’.


Sometimes – all you need – is one great man.
Lest we forget.

Drupal on Mac

May 9, 2009

snapshot2
Tried and tested, here are the steps:

  1. Download MAMP (Macintosh, Apache, Mysql and PHP) and is the Apache, PHP and MySQL stack for Mac OS X!
  2. Download latest Drupal (6.11 as of today)
  3. Install MAMP by
    • double-clicking the zip file do to extract the dmg file.
    • double clicking on the dmg file to mount it.
    • move the resulting MAMP folder into the applications folder, and unmount the disk image.
  4. Now, prepare for Drupal installation by following the steps below:
    • double-clicking the zip file do to extract the dmg file.
    • double clicking on the dmg file to mount it.
    • move the resulting Drupal folder into the applications folder.
    • you could alternatively rename the folder to drupal by removing version numbers.
  5. Start MAMP, by selecting the MAMP favicon for the application (found in ~/applications/MAMP/). Both Apache and MySQL servers should be running with green lights on.
  6. Point the browser to http://localhost:8888/MAMP/drupal/ and you are ready to go.
  7. Make sure to verify requirements displayed on the initial screens (relating to renaming the default.settings.php to settings.php and increasing PHP memory limit) along the way.

Wanna Write In Sinhala?

May 8, 2009

සිංහලෙන් ලියමු.

    Install a sinhala font. On MacOS X, just drop the font in ~/library/font folder.
    Install FireFox Plugin Sinhala Transliteration
    Use F8 to toggle language
    As you type, browser will display text in Sinhala. Off you go!

Podcast: Enterprise Use of Mashups and Upcoming WSO2 Mashup Server Release

May 5, 2009

In mashup 2.0 podcast, Keith Chapman talks to OxygenTank on the role of mashups in an enterprise setting and the upcoming componentized release of the WSO2 Mashup Server.

OSGi, Componentization, Virtualization and Dashboards

May 1, 2009

In yesterday’s Web panel discussion, WSO2’s Paul Fremantle and Sanjiva Weerawarana did a brilliant job answering questions from audience on contemporary topics in relation to SOA, middleware and the WSO2 stack. Initial discussion covered ground on the OSGi hype, WSO2’s adoption of the OSGi technology with its release of WSO2 Carbon, and its limitations. Sanjiva stated that pragmatic Carbon installations tends to take off with the adoption of a single product, which is then extended as per additional needs – rather than an installation that begins with the Carbon core, an enhanced with components. This seems more evident when we dive into popularus use cases driving middleware componentization. They are:

  • those who do not want to run separate products in multiple server instances in order to get a job done.
  • users who were frustrated with having to make a all-or-non decision taking on propriety middleware solutions – which meant they’d have to throw away all of their existing middleware in order to accommodate a new vendor.

The value of componentization, as Sanjiva pointed out, does not stop there. In fact, componentization has enabled innovative combinations of components in customer sites, that’s fused much more value added usage of WSO2 middleware, that was not envisioned at the point these compoenents were written. This to me is one of the greatest joys of technology. To watch new technology come out of research is certainly exciting, however, it is much more exciting to see the actual usage of a technology as it reaches the end users, which at time is far more outreaching that the technology initially planned. These innovative use cases then fuels additional research in that area of technology adoption.

Enforcing this cycle more rapidly means, there is constant feedback that results in continuous improvement to the technology in question. It is the value proposition behind the concept “release early, release often“.

As Paul and Sanjiva pointed out, componentization fits in very well with cloud computing and on-demand computing arena, in which users try squeeze in more and more value out of a single instance. With multiple virtualized platforms sitting in a single instance, virtualization stands to benefit greatly from componentization that leaves out having to live with fat and bloated solutions in cloud instances that would takes up considerable administrative efforts related to management and scalability.
On the cloud front, Sanjiva also emphasized the need to go a step forward from simply using it to host applications, which on its own clearly have merits, to actually host applications that are componentized. He referred to these as appliances – application component configurations that are assembled to meet very specific usage requirement,  reducing the total foot print of the installation. Along the same path, Paul mentioned that cloud computing with componentization could actually make the running of a data center a lot more efficient. They revealed WSO2 plans to offer its entire middleware stack on Amazon and Eucalyptus cloud infrastructures, just this same way.

In the presentation frontier, Paul mentioned WSO2 efforts in building a Carbon UI. He illustrated the the need for a business health monitoring portal requirement within an SOA. Such a system would then alert the health status of component deployments while exposing services that are otherwise distributed. A JSR-168 and iGoogle compatible personalized and componentized UI server solution is already in WSO2 agenda.