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

« Previous Version 4 Next »



  • Broadly approachable
  • Hit the ground running
  • Interoperable
  • Scalable and forward-looking
  • Fits the approach of the Fluid community: functional, declarative, Web-oriented

Broadly approachable means we can reach out to a large number of Web developers, allowing them to get involved in the Engage community and technology using skills and languages they may already have some familiarity with. Looking inward, the Fluid community needs to hit the ground running for Engage, building the services layer in technologies that are familiar to us and that will ensure we can start development with a minimum ramp-up time. Interoperability is primary goal of Engage, ensuring that our technologies will work with a wide range of existing authoring tools, content management systems, and other technology infrastructure commonly found in museums and on the Web. The Engage services layer needs to fit in well and play nice. At the same time, it needs to be scalable and forward-looking, allowing museums to invest in Engage over long run, without fear that it will slow down impossibly when confronted with large collections, and that it won't quickly go obsolete.

Candidates We Considered

  • PHP
  • Ruby + Merb
  • Python + CherryPy
  • JavaScript
    • Rhino on the JVM + Servlets + JSGI
    • Embedded next-gen runtime: v8cgi and others

Some Background Thinking

JavaScript on the Server

Portability and JSGI

Next Generation Runtimes

Rhino and the JVM

Tying it all Together

  • No labels