Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Rough Architecture Notes from the Fluid UToronto Team's Whiteboard

These are just notes; they don't make sense yet.

Component Framework Architecture

Component APIs

  • What does a component look like?
  • How does it get used?
  • How is it customized?
  • How are new components built?


  • Relationships between components
  • Proxying to the server

Server-side Binding Layer

  • AJAX communication with the server
  • REST-based?
    • Small number of actions: "verbs"
      **Lots of names: "nouns"
  • Lifecycle supports?

Transformation Flow

  • Compare metadata and preferences
  • If okay, do nothing
  • Otherwise, request an alternative component
  • Select from alternatives or use initial component

Component Repository

  • Mirrored within the application (ie. doesn't require a dependency on a 3rd party server)
  • Options:
    • Repository is just a file system: client-side transformation engine does all the work of finding matches
    • Repository is smart: implemented in Java or JavaScript or anther language, and can respond to requests from a lighter-weight client-side transformation engine
  • No labels