The Community for Technology Leaders
2013 IEEE International Conference on Services Computing (2006)
Chicago, Illinois
Sept. 18, 2006 to Sept. 22, 2006
ISBN: 0-7695-2670-5
pp: xxxix
E. Michael Maximilien , IBM Almaden Research Center San Jose, CA
ABSTRACT
<p>One of the interesting aspects of the Web 2.0 ?evolution? is the wide-availability of various Web applications as APIs or Web services. These APIs expose informational services on the Web and take many forms of remote invocation of functions using standard Web protocols and XML for data representations, e.g., REST, SOAP/WSDL, XML-RPC, and other approaches. The services (or APIs) are also usually accompanied by user facing Web applications for human-consumption. Canonical examples are Google Maps, Yahoo! Flykr and del.icio.us, EVDB?s Eventful?s application and API, Amazon.com?s S3, ECS, Alexa, and many others.</p> <p>The Ruby programming language and its Rails framework are ideal for programming Web applications and services in the Web 2.0. Ruby?s modern and dynamic features make it an excellent language for rapid prototyping and integration of various Web services. Rails? superb support for rapid Web application development, database access, and AJAX, make it well suited for creating front-ends and back-ends to the next generation of Web applications and services.</p> <p>In this tutorial we will take a hands-on deep-dive into the Ruby and Rails platform and learn how they can be used to: (1) create Web applications backed by a relational database, (2) consume Web services, (3) create and deploy APIs or Web services, and (4) mashup of existing Web services and applications. No a priori knowledge of Ruby or Rails is required - although some programming in a modern OO language and Web application development are definite plus.</p>
INDEX TERMS
null
CITATION
E. Michael Maximilien, "Web Services on Rails: Using Ruby and Rails for Web Services Development and Mashups", 2013 IEEE International Conference on Services Computing, vol. 00, no. , pp. xxxix, 2006, doi:10.1109/SCC.2006.118
107 ms
(Ver )