Customizing the RESTAdapter

In Ember Data, the logic for communicating with a backend data store lives in the Adapter. Ember Data’s Adapter has some built-in assumptions of how a REST API should look. If your backend conventions differ from these assumptions Ember Data makes it easy to change its functionality by swapping out or extending the default Adapter.

在Ember Data中，处理与后台数据仓库通信的逻辑是通过Adapter来完成的。Ember Data适配器内置了一些关于REST API的假定。如果后台的实现与Ember Data假定的惯例不同，那么通过扩展缺省的适配器可能很容易的实现。

Some reasons for customizing an Adapter include using underscores_case in your urls, using a medium other than REST to communicate with your backend API or even using a local backend.

有时因为一些原因需要自定义适配器，例如需要使用下划线风格的URL，使用REST外的其他媒介来与后台通信，或者是使用本地后台.

Extending Adapters is a natural process in Ember Data. Ember takes the position that you should extend an adapter to add different functionality instead of adding a flag. This results in code that is more testable, easier to understand and reduces bloat for people who may want to subclass your adapter.

扩展适配器在Ember Data中是一个常见的过程。Ember的立场是应该通过扩展适配器来添加不同的功能，而非添加标识。这样可以使得代码更加容易测试，更加易于理解，同时也降低了可能需要扩展适配器的用户的代码。

If your backend has some consistent rules you can define an ApplicationAdapter. The ApplicationAdapter will get priority over the default Adapter, however it will still be superseded by model specific Adapters.

如果后台具有一定的一致性规则，那么可以定义一个ApplicationAdapter。ApplicationAdapter的优先级比缺省的适配器高，但是又会被模型特定的适配器取代。

App.ApplicationAdapter = DS.RESTAdapter.extend({
    // Application specific overrides go here
});

If you have one model that has exceptional rules for communicating with its backend than the others you can create a Model specific Adapter by naming an adapter “ModelName” + “Adapter”.

如果一个模型的后台有一些特殊的规则，那么可以定义一个模型特定的适配器，并将适配器命名为：”ModelName” + “Adapter”。

App.PostAdapter = DS.RESTAdapter.extend({
  namespace: 'api/v1'
});

By default Ember Data comes with several builtin adapters. Feel free to use these adapters as a starting point for creating your own custom adapter.

缺省情况下，Ember Data内置了一些非常有用的适配器。可以根据自己的实际情况，选择其中之一作为起点来自定义适配器。

• DS.Adapter is the basic adapter with no functionality. It is generally a good starting point if you want to create an adapter that is radically different from the other Ember adapters.

• DS.Adapter是最基础的适配器，其自身不包含任何功能。如果需要创建一个与Ember适配器有根本性区别的适配器，那么可以这里入手。

• DS.FixtureAdapter is an adapter that loads records from memory. Its primarily used for development and testing.

• DS.FixtureAdapter是一个用来从内存中加载记录的适配器，常用于开发和测试阶段。

• DS.RESTAdapter is the most commonly extended adapter. The RESTAdapter allows your store to communicate with an HTTP server by transmitting JSON via XHR. Most Ember.js apps that consume a JSON API should use the REST adapter.

• DS.RESTAdapter是最通用的扩展适配器。RESTAdapter可以实现store与HTTP服务器之间通过XHR交互JSON数据。大部分使用JSON API的Ember应用都应该使用RESTAdapter。

• DS.ActiveModelAdapter is a specialized version of the RESTAdapter that is set up to work out of the box with Rails-style REST APIs.

• DS.ActiveModelAdapter是一个RESTAdapter的特列，用于与Rails风格的REST API协同工作。

Customizing the RESTAdapter

自定义RESTAdapter

The DS.RESTAdapter is the most commonly extended adapter that ships with Ember Data. It has a handful of hooks that are commonly used to extend it to work with non-standard backends.

DS.RESTAdapter是Ember Data提供的一个最通用的扩展适配器。它提供了一些非常有用的，可以扩展来与非标准化的后台接口通信的钩子。

Endpoint Path Customization

自定义端点路径

The namespace property can be used to prefix requests with a specific url namespace.

namespace属性用来指定一个特定的url前缀。

App.ApplicationAdapter = DS.RESTAdapter.extend({
  namespace: 'api/1'
});

Requests for App.Person would now target /api/1/people/1.

App.Person的请求将会发至/api/1/people/1。

Host Customization

自定义主机

By default the adapter will target the current domain. If you would like to specify a new domain you can do so by setting the host property on the adapter.

缺省情况下，适配器认为主机是当前域。如果希望指定一个新的域，那么可以通过设置适配器的host属性来指定。

App.ApplicationAdapter = DS.RESTAdapter.extend({
  host: 'https://api.example.com'
});

Requests for App.Person would now target https://api.example.com/people/1.

App.Person的请求将会发至https://api.example.com/people/1。

Path Customization

自定义路径

By default the RESTAdapter will attempt to pluralize and camelCase the model name to generate the path name. If this convention does not conform to your backend you can override the pathForType method.

缺省情况下，RESTAdapter尝试将模型名进行驼峰化和复数化来作为路径名。如果这种惯例并不符合使用的后台接口，可以通过重载pathForType方法来实现。

For example, if you did not want to pluralize model names and needed underscore_case instead of camelCase you could override the pathForType method like this:

例如，并不需要将模型名称复数化，需要采用下划线分割的模式替代驼峰命名，那么可以这样来重载pathForType方法：

App.ApplicationAdapter = DS.RESTAdapter.extend({
  pathForType: function(type) {
    return Ember.String.underscore(type);
  }
});

Requests for App.Person would now target /person/1. Requests for App.UserProfile would now target /user_profile/1.

App.Person的请求将会发至/person/1。 App.UserProfile的请求将会发至/user_profile/1。

Authoring Adapters

创作适配器

The defaultSerializer property can be used to specify the serializer that will be used by this adapter. This is only used when an model specific serializer or ApplicationSerializer are not defined.

defaultSerializer属性可以用来指定适配器使用的序列化对象。这只在没有模型特定的序列化对象，也没有ApplicationSerializer的情况下。

In an application, it is often easier to specify an ApplicationSerializer. However, if you are the author of a community adapter it is important to remember to set this property to ensure Ember does the right thing in the case a user of your adapter does not specify an ApplicationSerializer.

在一个应用中，指定一个ApplicationSerializer比较容易。但是如果自定了一个通信的适配器，并且没有指定一个ApplicationSerializer，那么设定defaultSerializer属性，来确保Ember的行为正确性比较重要。

MyCustomAdapterAdapter = DS.RESTAdapter.extend({
  defaultSerializer: '-default'
});

Community Adapters

社区适配器

If none of the builtin Ember Data Adapters work for your backend, be sure to check out some of the community maintained Ember Data Adapters. Some good places to look for Ember Data Adapters include:

如果Ember Data内置的适配器并不能很好的与使用的后台工作，可以查看社区维护的Ember Data适配器，看有不有合适的选择。可以去一下地方去查找：

• GitHub
• Bower