View comments | RSS feed

Mach II Development Guide - Contents

Release 1.2.1 (4/14/2005)

Printable Version

Contents

This Development Guide is structured as follows:

Introduction

This document explains how to develop applications using Mach II (Release 1.0.10), an MVC-based framework that implements the Implicit Invocation Architecture. You can read more about Mach II on the official Mach II website and Sean Corfield's unofficial Mach II website as well as Phil Cruz's Mach II information website. It is a living document, growing over time, incorporating feedback from Macromedia Web Team developers as well as the larger ColdFusion community, as the guidelines are 'proved' in our live environment.

Although this document is published as-is for the ColdFusion community, Macromedia's Web Team own the document and decide what goes into it. You may, however, take a copy of this document and modify it as you see fit to create your own development guide as long as you acknowledge this original document.

Conventions

The following conventions are used in this document:

[TBD: some comment in blue]
This indicates an issue which needs discussion and agreement within WTG.
Some comment crossed out in gray
This is a Macromedia-specific issue which is provided as an example of how the Macromedia Web Team handle an issue.

Comments


austinnichols101 said on Feb 18, 2004 at 9:59 AM :
Would it make any sense to use a 'cflock name=' for locking the shared-scope variables in machii? It would seem that by using name= that you wouldn't have to lock the application scope as a whole, for example.
SeanCorfield said on Feb 18, 2004 at 11:38 AM :
Re: cflock - the 1.0.9 release uses named locks around shared scope variables in mach-ii.cfm.
That ensures that all of the configure() methods are thread-safe (and therefore do not need locks).
If a listener, event filter or plugin method updates variables scope data (which is implicitly in application scope), then you would need to use a (named) lock to ensure thread safety.
Andrew Mercer said on Jan 10, 2005 at 6:51 AM :
Hi Sean,

In section 'Mach II Core Files' it has the files can be installed to the CF document root or in a Custom Tag Path. Should that actually be a mapped path (ColdFusion Mappings)?
SeanCorfield said on Jan 10, 2005 at 7:39 AM :
Andrew,

Although you will need a mapping to include the core mach-ii.cfm file (unless you copy it locally into your application), the more important piece of setup is to use a custom tag path so that the Mach II CFCs can be found.
ColdFusion uses custom tag paths to look for both custom tags and for components.
jaz_wd said on Mar 30, 2005 at 8:35 AM :
I need to know if Mach-II Works with CFMX 7.0.
SeanCorfield said on Mar 30, 2005 at 9:02 AM :
Yes, Mach II works flawlessly on ColdFusion MX 7. About a quarter of the fifty or so applications on macromedia.com are built with Mach II and macromedia.com has been running CFMX 7 since early February.
No screen name said on Aug 10, 2006 at 3:20 PM :
I am wanting to make seperate xml files for different projects. Is there something that I can alter or change to do so? So one tool has it's own set of views, listeners, and event-handlers.
SeanCorfield said on Aug 12, 2006 at 2:03 PM :
Whilst Mach II does not support multiple XML file, you can have multiple Mach II applications, each with its own XML file, that all share the same ColdFusion application scope (and session scope, so you can have single sign-on).

 

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/wtg/public/machiidevguide/index.html