And REST constrains
architecture in a way that has been found to be applicable to most applications,
so it is a reasonable default for new architectures. The conventions of
ActiveResource layer on top of these constraints in a way that is friendly to Rails/
ActiveRecord applications, and not very difficult to integrate with other applications.
Case Study: Amazon S3 | 231
Action Web Service
Action Web Service (AWS) is a client and server library for SOAPand XML-RPC
web services. It used to be the default web service component in Rails, but it has
actually since been dropped from Rails 2.0 in favor of ActiveResource and RESTful
interfaces.
AWS is still being maintained as a separate library, and is still a good choice for those
who need to interoperate with SOAPor XML-RPC applications. It is discouraged for
greenfield development, though; current best practices support the use of RESTful
HTTParchitectures. Thus, we will not go into detail here on its usage. API Documentation
for AWS is available at http://aws.rubyonrails.org/, and the library itself
can be installed as a gem (gem install actionwebservice).
Case Study: Amazon S3
Amazon S3 (Simple Storage Service) is an online file-storage web service provided by
Amazon. It is unique among online storage services in several ways:
??? It has a no-minimum pricing structure. Storage is billed by the GB-month, bandwidth
is billed by the GB, and there is an additional charge per GET, PUT, and LIST
request.
Pages:
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361