Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

3. Anatomy of a Robotlegs application > How a Robotlegs application gets things...

How a Robotlegs application gets things done

Although every Robotlegs application solves a unique problem, the ways in which the objects solving that problem cooperate and communicate are consistent. The tiers of the application—models, views, controllers and services—mostly communicate through a shared eventDispatcher. We’ll look at each layer in more detail later, but for now, a good place to start is with an overview of how the layers come together.

An overview of how a Robotlegs application gets things done
Figure 3-3. An overview of how a Robotlegs application gets things done

Architecture begins with Events and Commands

When you’re setting out to build your first Robotlegs application, you’ll probably wonder where to begin. Of course, views are always satisfying, and clients like to get their hands on something they can see, but the real lever you can pull when architecting a Robotlegs application is the controller layer: Events and Commands.


  

You are currently reading a PREVIEW of this book.

                                                                                                                    

Get instant access to over $1 million worth of books and videos.

  

Start a Free 10-Day Trial


  
  • Safari Books Online
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint