Building ColdFusion services with ColdSpring and Reactor, part 3

Submitted by Falken on Sun, 05/20/2007 - 11:23

Our previous article discussed the top-most tier in the stack, Services, and it is to the next layer, the Managers, that we now turn.

Managers are tasked with implementing the buisness process for a single task, observing any rules such as change logging. They hold all your logic about how to actually do the things the client asked the Service to do i.e. update the database via the Data layer, send a notification and then update something else.

Building ColdFusion services with ColdSpring and Reactor, part 2

Submitted by Falken on Sun, 03/25/2007 - 14:47
At the top of our tiers of ColdFusion objects, we have the Service.
Services deal with making sure the underlying Managers who perform the work are abstracted from the way the Service is called. Typically this means a service will enforce authentication requirements, though authorisation may be dealt with here too rather than with in a manager particularly if it is a simple 'is user in role' task. If you do this though you must be careful to make the same checks when the Manager is invoked in other ways - like from another Manager.

Does Mark Drew ever sleep ?

Submitted by Falken on Wed, 03/07/2007 - 14:12

Not content with getting a point release out the door recently, CFEclipse author Mark Drew has just posted yet another tweak to the 1.3 version that fixes a minor secure FTP issue and also updates the icon artwork.

You can read all about it here, update now to get the latest and greatest version of the ColdFusion Eclipse plugin.

Building ColdFusion services with ColdSpring and Reactor, part 1

Submitted by Falken on Mon, 03/05/2007 - 12:44

We'd best start the real meat of this series of articles by explaining what we want to achieve, and defining a few key terms.
Later articles will discuss key parts in more detail.

The approach I outline builds a tiered service orientated ColdFusion architecture, A 'tiered' approach means we construct things by layering one set of CFCs atop another, with limited interfaces between layers. Layers may only call upon things at or beneath them.
Each layer should perform one task, and deeper layers should have less abstraction.

Why would we do this ?

CFEclipse 1.3 thoughts

Submitted by Falken on Sat, 01/27/2007 - 16:57

As I'm sure you've all noticed by now, the number one IDE (all right, IDE plugin) for ColdFusion developers, CFEclipse, has been updated to version 1.3, but what does this mean for your daily life ?

By accident, I noticed that pressing F1 while in a tag no longer fires up the browser - you get nice help in a new side panel. This should mean no more flicking back to Adobe's site to look up something, hurrah !

Why use CFCs in ColdFusion

Submitted by Falken on Tue, 12/12/2006 - 19:35
From my point of view, we're now an order of magnitude or more above simply asking the user a few questions on a form and feeding those into a query and printing out the query in a table.

We want to break the request/response cycle, we want to make out code testable so we can fix things with out worrying about what we broke, we want to be able to reuse code and we want to be able to use the same code from an AJAX app, a CFML page, and a Flex application. That's just of the top of my head.