New version Cairngorm 2.2.1:support for Flex 2.0.1 with Hotfix 2 and LiveCycle Data Services 2.5.x.

There is a minor change from Cairngorm 2.2 to Cairngorm 2.2.1.

They have changed ServiceLocator to reflect moving of classes to LiveCycle Data Services (fds.swc). The main aim is to align Cairngorm with the moving of SWC libraries in Flex 2.0.1 with Hotfix 2 and LiveCycle Data Services 2.5.x.

Cairngorm was developed to work on request/response communication mode. To work on Data Oriented Architecture is still a challenging task.It seems that Adobe Consulting is working on this area.We can expect some significant changes in next Cairngorm release.I am looking forward to the next big release of Cairngorm with all these changes.

1 comment:

Steven said...

So i'm going to blog on this in more detail in the weeks ahead, but I want to clarify; if you are building applications with current versions of Cairngorm, and you are invoking services using RemoteObject, WebService or HTTPService, then there are no big changes coming; everything is going to continue as planned, and our best-practices for SOA applications remain the same.

However, our deep thinking has been around creating applications that leverage LiveCycle Data Services, in particular Data Management Services. As you correctly point out, if that's your application archtecture, then we're doing a lot of thinking on what we should let the Flex/LCDS framework do well, and what Cairngorm should do well, and how the 2 interoperate. We presented (Peter Martin presented in Chicago, Alistair McLeod will present in Barcelona) our current thinking for feedback and review, but it's by no means baked into a Cairngorm release just yet.

I just want to be clear here -- if you're using Cairngorm or thinking of using it, don't be reticent to do so because you think it's all going to change in a few weeks. That's totally not the case.

But if you're using Data Management Services, we'll have some lessons learned to share, and the lessons that we continually apply, we'll work into Cairngorm as additional best-practice alongside the current best-practice.

And backwards compatibility remains a continued principle upon which we will operate.