Less Chatter, More Work Continued from page 37 Conclusion The presence of SOAP, WS-*, and ADF in an architectural diagram for a REST article may raise some eyebrows, but recall that all that matters is how the original resource request looks to the client application. REST prescribes access to information via addressable resources; it does not dictate internal implementation. The client sees a REST resource and gets the answer the user wants quickly. Much has been written in the Esri realm about the power and usefulness of COM utilities and SOEs. Developers and architects need to remember that the RESTful nature of application architecture need not stop where the Esri REST API toolbox does. That's the beauty of REST: it allows developers to bolt together high-performance, URI-based services and application components that may or may not be of their own making. David Bouwman Brian Noyle That's the beauty of REST: it allows developers to bolt together high-performance, URI-based services and application components that may or may not be of their own making. Providing server-side components, accessible via a REST resource, in this way is an excellent means of developing focused, user-friendly applications with advanced capabilities not currently available in the ArcGIS Server SOAP and REST APIs. Furthermore, this approach hides complexity from the user, delivers high performance, and represents a simple reorganization of Esri technologies most GeoWeb developers are already used to using. For more information, contact David Bouwman, CTO and Lead Software Architect DTSAgile Fort Collins, Colorado E-mail: dbouwman@dtsagile.com or Brian Noyle, Senior Software Architect DTSAgile Fort Collins, Colorado E-mail: bnoyle@dtsagile.com About the Authors David Bouwman has been designing and developing GIS software for the last 12 years. His projects have ranged from small Web sites to statewide enterprise forest management systems. Over the last few years, he has been leading a team of developers in the pursuit of great software built in a sane manner. The combination of an agile process with pragmatic development practices taken from extreme programming has led his firm to develop a highly optimized methodology for creating solid software. When he is not attached to a computer, Bouwman is often found mountain biking on the trails around Fort Collins. Brian Noyle originally trained as a global change biologist and tundra botanist. He has nearly 10 years' experience as a GIS software developer and architect. His professional and technical interests are primarily focused on moving clients toward more standard architecture and development practices and patterns to facilitate a closer integration of GIS with the standard IT enterprise. Noyle has extensive experience in full software life cycle management with a focus on delivering through agile project management methods. When he's not in the office, he can be found on his mountain bike, picking a bluegrass lick on the guitar, or standing in a river waving a stick (at trout). © 2009 Laserfiche. Laserfiche is a registered trademark of Compulink Management Center, Inc. Service x Speed = Government 2.0 Laserfiche® digital document management puts you on the fast track towards more focused, more agile and broader-ranging public service. And it does it all while making your job a lot easier. That's 21st-century government. That's Government 2.0. Discover how Laserfiche integrates with Esri® GIS software to bring a world of information to staff and citizens. Visit laserfiche.com/arc or call (800) 985-8533 to get answers now. Run Smarter® 38 ArcUser Summer 2009 www.esri.com